developlisted

# Skill Developer Workflow Implement skill development issues through iterative planning, TDD-governed implementation, and review cycles. ## When to Use - Implementing a GitHub issue that creates or modifies skills, plugins, agents, or hooks - Issue requires TDD-governed phases (baseline → implement → verify) - Work involves SKILL.md frontmatter, workflow references, agent prompts, or hook scripts ## When NOT to Use - General code changes unrelated to skill/plugin authoring - Quick validation or auditing — use `/plugin-dev` instead - Scaffolding a new plugin from scratch — use `/plugin-dev:create` instead ## Quick Reference | Phase | Action | Exit Condition | |-------|--------|----------------| | 0. Setup | **MUST** create feature branch | On feature branch (NOT main/master) | | 1. Context | Read issue + detect skill files | Requirements clear, skill files noted | | 2. Plan | Draft implementation plan | Plan complete | | 3-4. Validate | Gemini review loop (max 5) | `APPROVED` status | | 4.5. Baseline (RED) | TODO: #163 — capture baseline behavior | Baseline captured (or skipped pending #163) | | 5-7. Implement (GREEN) | Write minimal skill addressing failures | All tasks done + criteria met + tests passing + validation passing | | 7.5. Verify (REFACTOR) | TODO: #163 — compare against baseline | Benchmark passes (or skipped pending #163) or escalated | | 8-9. Review | Council review (max 3) | `APPROVED` status | | 10. Finalize | Commit + PR | PR created | | 11. Cleanup