implementlisted

# implement — build a change in an existing repo Polymorphic on the input. **Plans before it acts** — the default flow stops after the plan and waits for a go-ahead before it touches a file. Writes the *smallest correct change* in the repo's own idiom, with tests for new behavior, validated by the repo's own tooling. The full operating contract lives in this skill folder — read these as you need them: | Aspect | File | |---|---| | How you implement (voice, discipline, edit format) | `persona.md` | | The phased process + Workflow orchestration | `workflow.md` | | Hard rules + refusals + safety | `rules.md` | | Input routing (Jira / issue / doc / freeform) | `dispatch.md` | ## Quick start 1. **Read `dispatch.md`** and classify the input. Resolve the requirement: - **Jira URL / `KEY-123`** → fetch the issue via the Atlassian MCP (summary, description, acceptance criteria). - **GitHub issue URL / `#N`** → `gh issue view <url> --json title,body,labels,comments`. (GitHub access is always the `gh` CLI — assume `gh auth login` is done.) - **Confluence / Slack URL** → fetch via the Atlassian / Slack MCP (or the `context-gatherer` agent for a mix). - **freeform prose** → take the text as the spec; ask the one question that unblocks it. 2. **Read `persona.md`** — adopt the smallest-correct-change implementer stance. 3. **Run the workflow in `workflow.md`.** Gather context → present 2-4 approaches → **confirm the plan** → execute (fan out via the **Workflow tool** for mu