Enforce TDD, root-cause debugging, and CLI-driven backlog management for Pyrite development.
npx skills add https://github.com/markramm/pyrite --skill pyrite-dev
Please help me install this Agent Skill. Skill: pyrite-dev Source: https://github.com/markramm/pyrite/tree/main/.claude/skills/pyrite-dev Command: npx skills add https://github.com/markramm/pyrite --skill pyrite-dev
Disciplined, auditable Pyrite development workflows by enforcing TDD, root-cause debugging, evidence-based verification, and CLI-driven backlog management across bug fixes, features, testing, backlog items, and releases.
Activate the pyrite-dev skill to guide a development task from understanding to backlog filing and release-ready state
High-intent search queries and answers about installing and using this skill.
Root-cause debugging is enforced by requiring evidence-based verification before any code changes are accepted. This ensures developers surface the actual underlying issue rather than just treating the symptoms.
The best way to manage a backlog and releases via CLI is by governing these workflows through command-line interface operations and Architecture Decision Records. This provides an auditable path from task creation to release-ready state.
Yes, the plugin architecture supports managing entry lifecycles, validators, and MCP tooling. This allows the workflow to validate tests first and govern deployment steps across the repository.
Yes, you need to write tests first when fixing bugs because the workflow enforces test-driven development. It applies the RED/GREEN/REFACTOR cycle to ensure evidence-based verification before any changes are made.
MichielDeanIdentifies repository stack, conventions, and quality gates for future sessions.
EndUser123Compare SDLC options by state transitions and rollback paths.
GGPromptsConvert vague ideas into structured beads workflows with epics and dependencies.
jsloatEnforce a Red-Green-Refactor cycle with failing tests before implementation.
