implement-feature

Implement planned software features using TDD with human testing checkpoints.

5|Updated Jan 2, 2026
One-click install
npx skills add https://github.com/suzbot/petri --skill implement-feature-suzbot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-feature
Source: https://github.com/suzbot/petri/tree/main/.claude/skills/implement-feature
Command: npx skills add https://github.com/suzbot/petri --skill implement-feature-suzbot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of implementing planned software features or steps, ensuring adherence to architectural patterns and incorporating rigorous testing methodologies.

Core Features & Use Cases

  • Guided Implementation: Follows a pre-defined plan from docs/ for feature development.
  • Test-Driven Development (TDD): Emphasizes writing tests first and implementing minimal code to pass them.
  • Human Testing Integration: Includes mandatory checkpoints for user verification.
  • Documentation Updates: Facilitates updating documentation post-implementation.
  • Use Case: When a new feature is defined in the project plan, this Skill guides the developer through writing tests, implementing the code, and ensuring it's manually verified and documented.

Quick Start

Use the implement-feature skill to build the next planned step for the user profile feature.

Frequently Asked Questions about implement-feature

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement planned software features using TDD?

To implement planned software features using TDD, this Skill validates your pre-defined plan document against architecture patterns, then executes the development steps by writing tests first, implementing minimal code to pass them, and enforcing human testing checkpoints.

What's the best way to ensure my feature implementation matches existing architecture patterns?

To ensure feature implementation matches existing architecture patterns, this Skill validates your pre-defined plan document against those patterns before executing any development steps, ensuring structural consistency and adherence to project standards.

Do I need a pre-existing plan document to start feature development?

Yes, you need a pre-defined plan document in the `docs/` directory to start feature development. This Skill requires adherence to that existing plan to guide the Test-Driven Development execution and human testing checkpoints.

How does test-driven development work with human testing checkpoints?

Test-driven development with human testing checkpoints works by first writing tests and implementing minimal code to pass them, then pausing execution at mandatory checkpoints for user verification, ensuring both automated and manual validation before updating documentation.

Can I update documentation automatically after implementing a feature?

You can update documentation after implementing a feature through this Skill's post-implementation workflow, which facilitates documentation updates as a specific checkpoint following the successful execution and human verification of your test-driven development steps.