Implements tickets from a spec using TDD with verification and code review.
npx skills add https://github.com/MoofonLi/dev-ready --skill implement-moofonli
Please help me install this Agent Skill. Skill: implement Source: https://github.com/MoofonLi/dev-ready/tree/main/.agents/skills/implement Command: npx skills add https://github.com/MoofonLi/dev-ready --skill implement-moofonli
docs/handoff/<version>/phase-N/tickets/, staying inside the declared file footprint. - Mandatory TDD cycle: Enforces red (failing test) → green (minimal implementation) → refactor, followed by a verification loop of uv sync --dev, uv run pytest, and uv run ruff check .. - Built-in review and safe git behavior: Runs /code-review when a ticket is green and never performs state-changing git operations without explicit permission. - Use Case: After running to-spec and to-tickets, ask your agent to implement the next unblocked ticket; it writes failing tests first, implements the minimal code, runs the full verification loop, and reports a ready-to-commit Conventional Commit message. ## Quick Start Ask your coding agent to implement the next unblocked ticket from the current phase using the implement skill.High-intent search queries and answers about installing and using this skill.
Work one frontier ticket at a time, writing a failing test first, then the minimal implementation to pass it, then refactoring. After the code is green, run the verification loop of uv sync --dev, uv run pytest, and uv run ruff check . before marking the ticket done.
The internal Spec Loop runs grill-with-docs → to-spec → to-tickets → implement. Implementation is the last step, executed wearing the Engineer hat and then the Reviewer hat with /code-review.
No. State-changing git operations like commit, push, branch, merge, or reset require explicit permission for each specific action. Read-only git commands such as status, diff, and log are always allowed, and the agent reports a suggested Conventional Commit message instead.
Stop rather than grinding on the problem. Report the symptom, what was tried, and the suspected area in the session, optionally use /diagnosing-bugs for a bounded attempt, then move to the next unblocked ticket.
Run uv run pytest -m network only when the ticket touches fetch or pin behavior. It is the fourth step of the verification loop and is skipped for tickets that do not involve network-related code.
ClaudfatherExecutes ordered multi-phase plan docs as one governed sprint with cross-phase state tracking.
langadventurellcAutomate Git commits with conventional messages and pre-commit hook verification.
fefogarciaCoordinate parallel agents to trace execution and map entry points for debugging.
markus41Orchestrate multiple plugin agents across sequential, parallel, and fan-out/fan-in coordination models.