implement-issue
End-to-end workflow for implementing an OpenDataSuite GitHub issue — read the issue and roadmap, plan against acceptance criteria, implement with tests, verify, and open a PR. Use when asked to "work
SKILL.mdskills/implement-issue/SKILL.md
GitHubImplement an ODS issue
1. Understand
- Read the issue (GitHub MCP
issue_readorgh issue view N) including comments. - Find it in
docs/ROADMAP.md/.github/milestones.json: note milestone and whether it is critical-path. - Check dependencies: issues listed earlier in the same milestone table, or in an earlier milestone, that this one builds on. If a hard prerequisite is not done, say so and propose doing the prerequisite (or a minimal stub of its contract) first.
- If it is listed as a duplicate in ROADMAP §5, work on the canonical issue instead.
2. Plan
- Turn every acceptance-criteria bullet into a checklist item with the test that proves it.
- Identify crates touched. If a new crate or contract is needed →
new-crateskill. - If the issue says "ADR" or introduces a new persisted format / contract / dependency
class → write the ADR first with the
adrskill (can be the same PR). - For non-trivial issues, delegate to the
issue-plannersubagent and review its plan.
3. Implement
- Follow AGENTS.md rules (provider neutrality, conservative defaults, explainability,
determinism). Contracts go in
ods-sdk; vendor code inproviders/. - Add a fake implementation + conformance test for any new contract.
- Human output +
--jsonfor any new CLI command; snapshot-test both. - Keep scope to the acceptance criteria; file follow-ups as new issues (ask first).
4. Verify
- Run the
verifyskill. All checks must pass. - Ask the
architecture-guardsubagent to review the diff; fix any violations.
5. Deliver
- Conventional Commit messages; reference the issue (
Part of #N/Closes #N). - Push to the assigned branch. Open a PR only if the user asked; the body should map each acceptance criterion to evidence (test name, command output, file).