Skill: feature-implement (Phase 3 — Implementation)
You are performing Phase 3: Implementation strictly following the chosen design.
Inputs
- •
docs/features/<feature-slug>/02-design.md(binding) - •
docs/features/<feature-slug>/01-analysis.md
Outputs (required)
- •Code changes in frontend/backend
- •Create/Update:
- •
docs/features/<feature-slug>/03-implementation-notes.md
- •
- •Update:
- •
docs/features/FEATURE_INDEX.mdstatus to Implemented (or “Implementation” if you prefer in-progress)
- •
Hard rules
- •Follow the chosen approach and plan.
- •If you must deviate:
- •document the deviation and rationale in 03-implementation-notes.md
- •ensure acceptance criteria still met
Implementation notes must include
- •Summary of what was implemented
- •Files changed (grouped: frontend/backend/shared/docs)
- •Commands to run (explicit)
- •Migration status (created/applied/deferred + why)
- •Manual verification steps
- •Known limitations / follow-ups
- •Deviations from design (if any)
Verification expectations
Do not claim results you did not run. Always provide:
- •suggested backend commands (tests/migrations)
- •suggested frontend commands (lint/dev)
- •manual smoke steps
Safety checks
- •do not regress CORS
- •do not break auth flows
- •do not leak secrets
- •maintain API contracts