name	specrail-plan-tasks
description	Use when turning an approved SpecRail product and technical spec into the numbered `tasks.md` plan. Creates stable task IDs, owners, done-when conditions, verification commands, dependencies, and handoff notes without implementing the tasks.

SpecRail Plan Tasks

Use this skill to create or update the task plan before implementation.

python3 checks/route_gate.py --repo . --route implement --issue <issue-number> --state ready_to_implement --json

Write specs/GH<issue-number>/tasks.md.
Use stable task IDs such as SP<issue-number>-T1.
For every task, include owner, dependencies, done-when evidence, and verify commands.
Separate implementation tasks from verification and handoff notes.

Do not implement while planning tasks.
Do not remove human gates for readiness, spec approval, final review, merge, release, or security decisions.
Keep the plan small enough for one agent or a clearly partitioned thread lane.

name	specrail-plan-tasks
description	Use when turning an approved SpecRail product and technical spec into the numbered `tasks.md` plan. Creates stable task IDs, owners, done-when conditions, verification commands, dependencies, and handoff notes without implementing the tasks.

Use this skill to create or update the task plan before implementation.

python3 checks/route_gate.py --repo . --route implement --issue <issue-number> --state ready_to_implement --json

Write specs/GH<issue-number>/tasks.md.
Use stable task IDs such as SP<issue-number>-T1.
For every task, include owner, dependencies, done-when evidence, and verify commands.
Separate implementation tasks from verification and handoff notes.

Do not implement while planning tasks.
Do not remove human gates for readiness, spec approval, final review, merge, release, or security decisions.
Keep the plan small enough for one agent or a clearly partitioned thread lane.

specrail-plan-tasks