autonomous-dev

# Autonomous Development $ARGUMENTS Own one software-delivery run from its requested outcome to a reviewed, verified PR. Continue through reversible decisions within the user's approved scope, recording assumptions where they can be reviewed. Use existing skills for their actual work; this skill owns sequencing, state and the exit gate. ## Entry points | Input | Action | |---|---| | `setup` | Inspect the project and create its validation/tracker/QA configuration | | `run <brief, spec path, Jira key, issue URL or PR URL>` | Resolve the task, reuse existing work, then run the process | | `list` | List this repository's existing runs without changing state | | `resume <run-id>` | Read durable state, claim ownership and continue at the first unmet gate | | `status <run-id>` | Read state and report the next action; change nothing | A plain task description means `run`. `/workflow autonomous-development` routes here. A request only to review code stays with `/review`; an incident stays with the incident-response workflow. ## Setup and authorization Read [project configuration](reference/project-config.md) on first use or when project commands change. Check the target repository's instructions, KB, actual build/test commands and provider identities. Keep `issueTracker`, `codeHost` and `knowledge` separate. For Jira/RAG projects, read the [stack integration contract](reference/stack-integrations.md) before discovery and reuse it for resume, QA and finalization. Validate the r...