| name | specrail-implement |
| description | Use when implementing a SpecRail-governed issue after the implementation gate. Executes the scoped task plan, keeps changes tied to linked specs and acceptance criteria, runs deterministic verification, and preserves human approval, merge, and security boundaries. |
SpecRail Implement
Use this skill for the implement route.
Steps
- Read the linked issue, product spec, tech spec, and task plan.
- Run the implementation route gate when available:
python3 checks/route_gate.py --repo . --route implement --issue <issue-number> --state ready_to_implement --json
- If the gate returns
needs_human or blocked, stop and report the missing
evidence or gate.
- Implement only the scoped tasks. Search before adding files, workflows,
schemas, templates, policies, or public APIs.
- Keep machine-facing IDs in English and human-facing text in the selected
locale.
- Run focused verification for touched behavior, then run the pack check when
workflow assets changed:
python3 checks/check_workflow.py --repo .
- Record changed files, commands, results, and remaining human gates.
Boundaries
- Do not provide final approval.
- Do not merge without explicit human authorization and a passing PR gate.
- Do not publish secrets or private security details.
- Do not weaken tests or deterministic checks to make implementation pass.