rafaie/feature-kickoff
skills/feature-kickoff/SKILL.md
Create a work item documentation folder under spec/features/ (and ADR if needed).
$ install --global
skillsauthnpx skillsauth add rafaie/codex_home feature-kickoffInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 5, 2026, 6:20 AM140.9s7 files scanned
SKILL.md
- name:
- feature-kickoff
- description:
- Create a work item documentation folder under spec/features/ (and ADR if needed).
- Read project
AGENTS.md(repo root) andcodex.toml(if present) and follow conventions/commands. - Collect inputs: Work item ID (
S-<stream>-<nnn>, exampleS-core-001), title, goal, constraints.- Accept legacy dotted
FIDs only when updating older specs; create new work withS-<stream>-<nnn>.
- Accept legacy dotted
- Create a work item folder
spec/features/<work-id>-<slug>/(use actual work item ID).- Prefer repo templates under
spec/templates/if present. - Otherwise use this skill's
assets/default_*_template.mdfiles.
- Prefer repo templates under
- Create/update these documents inside the folder:
feature.md: problem, scope, acceptance criteria, design, ADR linksimplementation.md: implementation plan and chronological implementation logtest-plan.md: unit/integration/e2e/edge/smoke test plantest-results.md: commands run, outcomes, failures, fixesstatus.md: status, owner, next action, blockersevidence/README.md: directory placeholder and evidence index
- Fill the initial docs.
test-plan.mdmust include smoke details: scenario, fixture, pass/fail mode, artifact path.
- If no ADRs exist yet, create
spec/decisions/ADR-0001-initial-architecture.md(preferspec/templates/adr.mdif present). - If a major decision is required, create
spec/decisions/ADR-XXXX-<slug>.md(preferspec/templates/adr.mdif present). - Stop after writing docs. Do NOT implement code.
- End by listing the next 3 tasks.
- Tasks must be distinct (no duplicates).
- Use this default sequence unless the user asks for a different flow:
Run $spec-linter <work-id> to review the work item docs for gaps.Run $implementation-phase <work-id> to plan tests, write tests, and implement the work item.Run $ship-feature <work-id> to execute full checks, smoke evidence, ADR/docs/index updates, and final readiness output.
<work-id>must be the real ID for the folder you just created (example:S-core-001).- Keep each task line concrete and non-redundant.
Related Skills
rafaie/write-tests
testing
VerifiedTrustedCommunity
Add or improve tests based on a work item folder's acceptance criteria and test plan.
1SKILL.mdUpdated May 5, 2026
rafaie/test-runner
testing
VerifiedTrustedCommunity
Run quick/full checks consistently, include smoke, and summarize failures into actionable buckets.
1SKILL.mdUpdated May 5, 2026
rafaie/test-plan
testing
VerifiedTrustedCommunity
Create a work item test plan from acceptance criteria and add it to the work item docs.
1SKILL.mdUpdated May 5, 2026
rafaie/spec-linter
development
VerifiedTrustedCommunity
Review a work item documentation folder for clarity, testability, and completeness before implementation.
1SKILL.mdUpdated May 5, 2026