| name | dev-workflow |
| description | Use for any delivery-mode task that changes code or tests. Routes implementation work by risk and applicable branch skills before editing. |
| metadata | {"short-description":"Risk-routed dev workflow","requires":["references/dev-workflow.md"]} |
Purpose
This skill is the router for implementation work in this repository.
It decides which branch workflows are required for the current task.
When to use
Use this skill for any delivery-mode task that changes code and/or tests. It is mandatory in delivery mode. In research mode (see .agents/project-policy.yml), route through $research-workflow instead; promotion of research results into delivery paths re-enters this skill.
How to use
-
Open references/dev-workflow.md and fill it top-down.
-
Route by risk first (low | normal | high) and record why — full risk definitions and the required-outputs-by-risk table: references/dev-workflow.md §0.
1a) Declare the work-intent (feature default | poc | refactor | hardening) — full definitions and tie-breaks: references/dev-workflow.md §0a.
1b) Record the compat-mode whenever public/cross-module APIs are touched or the task reworks/consolidates/deletes — full definitions: references/dev-workflow.md §0b.
- Run the default implementation lane when required by risk — full lane: §1.
