Design Principles
1. Phase-based, not concern-based
Section titled “1. Phase-based, not concern-based”Each skill is a delivery phase that embeds its own discipline. TDD lives inside implement, not as a separate concern.
2. Convention over configuration
Section titled “2. Convention over configuration”Reads your repo’s CLAUDE.md / AGENTS.md for conventions. Sensible defaults for everything else.
3. Client-agnostic
Section titled “3. Client-agnostic”SKILL.md files. Works with any agent that reads them. No vendor lock-in.
4. Platform-agnostic
Section titled “4. Platform-agnostic”Claims work from GitHub, Linear, Jira, or any task board.
5. Spec-flexible
Section titled “5. Spec-flexible”Issue body, design doc, or OpenSpec directory. Your call.