aico-backend-plan_skill

Overview

This skill generates an ATOMIC, micro-level implementation plan for a single backend task in a TypeScript project. Each step is a single action that includes exact code, the files affected, and a verification command. The plan strictly follows TDD: Types → DB → Test (failing) → Implementation (passing) → API → Verification.

How this skill works

The skill reads the task specification from docs/reference/backend/tasks/{story}.md and constraints from docs/reference/backend/constraints.md, then breaks the task into atomic steps. It emits a numbered plan where each step lists Files, exact code to add or change (one small change only), and a shell command to verify the step. Steps are ordered to ensure tests fail first, then pass, and each step has a single verification command.

When to use it

• When you run the /backend.plan command for a specific backend task
• When you need micro-level, code-first steps with TDD verification
• When you want exact file edits and one-command verification per step
• When implementing a documented task from docs/reference/backend/tasks/
• When you must avoid architecture-level or high-level planning

Best practices

• Keep each step to one atomic change: one file create or one small edit
• Write a failing test before any implementation step (RED → GREEN)
• Provide exact TypeScript code and precise file paths in the step
• Use a single, reproducible verify command per step (e.g., npx tsc --noEmit or npm test -- -t 'name')
• Follow the rigid step order: Types → Database → Test → Implement → API → Commit

Example use cases

• Add a new DTO and interface file, then write a failing unit test for a service method
• Create a DB migration file, write a test expecting migration to expose a column, then implement repository changes
• Implement a single API route: add request/response types, failing integration test, handler code, then route registration
• Fix a single service method: add type, failing test, small implementation change, then verification
• Add validation: define types, failing validation test, implement validator, then update API payload handling