Spec Driven Development

Spec Driven Development

Use this skill to handle Programming tasks focused on requirements, acceptance criteria, contracts, edge cases, implementation from spec.

Workflow

1. Clarify the user outcome, constraints, current stack, and definition of done.
2. Inspect the local repository or provided artifacts before proposing changes.
3. Check official documentation when APIs, platform rules, SDK versions, policies, or production behavior may have changed.
4. For non-trivial choices, compare proven open-source patterns or examples and adapt ideas without copying incompatible code.
5. Implement the smallest production-ready change that satisfies the request.
6. Validate with the most relevant checks: tests, lint, typecheck, build, browser/device review, audits, or manual scenario.
7. Report changed files, commands run, remaining risks, and exact next steps.

Focus Checklist

• Define scope and assumptions explicitly.
• Prefer existing project conventions and tools.
• Handle loading, empty, error, permission, and edge states where relevant.
• Include security, privacy, performance, accessibility, and rollback considerations when they apply.
• Keep output actionable and evidence-backed.

Guardrails

• Do not expand scope beyond the agreed spec without recording assumptions.
• Do not perform destructive, paid, production, trading, publishing, or account-changing actions without explicit user confirmation.
• Do not expose secrets, private keys, tokens, cookies, personal data, or confidential business data.
• If validation is impossible, state exactly why and provide a manual verification path.