specrail-workflow

# SpecRail Workflow Use this skill as the entrypoint for SpecRail-governed repository work. Load a focused SpecRail skill after the route is known. ## Startup 1. Search before creating a new issue, spec, template, policy, schema, or workflow. 2. Read applicable `AGENTS.md`, then `AGENT_USAGE.md` and `PLAN.md` when present. 3. Read `workflow.yaml`, `states.yaml`, `labels.yaml`, and relevant templates. 4. Identify the route: - `triage_issue` - `write_spec` - `implement` - `review_pr` - `fix_ci` - `draft_release_note` 5. Run `checks/route_gate.py` for the selected route when the repository includes it. Treat `allowed` as permission to proceed, `warn` as proceed-with-caution, `needs_human` as a maintainer gate, and `blocked` as a stop condition. 6. When GitHub issue evidence is needed and the repository includes the adapter, collect it read-only: ```sh python3 checks/github_issue_evidence.py --github-repo <owner/repo> --issue <issue-number> --json > issue-evidence.json ``` ## Route To Focused Skills - Use `skills/specrail-triage-issue/SKILL.md` for issue classification, duplicate searches, label proposals, and triage handoffs. - Use `skills/specrail-write-product-spec/SKILL.md` for `docs/specs/GH<issue-number>/product.md`. - Use `skills/specrail-write-tech-spec/SKILL.md` for `docs/specs/GH<issue-number>/tech.md`. - Use `skills/specrail-plan-tasks/SKILL.md` for `docs/specs/GH<issue-number>/tasks.md`. - Use `skills/specrail-implement/SKILL.m...