typescript-coder-plan-spec

Provide the approved spec or change description and this Skill slices the work into phases by invariant, dependency, or migration boundary. Each phase gets a stated unlock reason, a smallest honest validation step, and rollback notes where the blast radius is real.

The plan assumes committed migrations with prisma migrate deploy, not migrate dev. Schema changes on existing data use expand-and-contract sequencing, with separate phases for schema introduction, backfill, and cleanup, plus options like NOT VALID constraints or CREATE INDEX CONCURRENTLY for live tables.

Use phased execution by default for non-trivial work touching multiple risk seams. Parallelization is only justified when write scopes are disjoint, lane dependencies are explicit, and a real fan-in checkpoint exists; shared migrations, contracts, or Redis protocols force phased ordering.

No. It owns only the planning layer between approved design and code execution: phase ordering, dependencies, validation, and rollback. Code writing, unresolved architecture decisions, and standalone test-plan design are handed off to neighbor skills.

The Skill refuses to fake completeness. It outputs a blocker list, pre-planning investigation steps, or a conditional plan with explicit assumptions instead of hiding unresolved design work inside executable phases.

Fastify inject() boots plugins but does not exercise onListen, WebSocket setup, or socket lifecycle. Plans touching listen-time side effects, streaming, or shutdown paths require stronger validation steps than route-level inject tests.