skills.rest
dallenpyrah
dallenpyrahCOMMUNITY
Explore all skills by this author →
GitHub

implement

Execute PRD or issue work with TDD, typechecking, and test suites.

Updated Jun 21, 2026
Search Tags:#code review#TDD#commit#implementation#PRD
One-click install
npx skills add https://github.com/dallenpyrah/pi --skill implement-dallenpyrah
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/dallenpyrah/pi/tree/main/skills/implement
Command: npx skills add https://github.com/dallenpyrah/pi --skill implement-dallenpyrah

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The implement Skill streamlines the process of executing work based on Product Requirements Documents (PRDs) or a set of issues, enhancing productivity and ensuring thoroughness.

Core Features & Use Cases

  • PRD-based Execution: Execute work precisely based on user-defined PRDs or issue lists.
  • Testing and Review: Supports TDD where possible and includes steps for regular typechecking, single test files, and full test suite execution.
  • Collaborative Workflows: Allows use of '/tdd' for pre-agreed seams and '/review' for work reviews.
  • Committing Work: Ensures that completed work is committed to the current branch for version control.

Quick Start

Use the implement skill to execute the work described in the attached PRD or issue list.

Frequently Asked Questions about implement

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

FAQPage Schema
How do I automate code implementation from a PRD or issue list?▼

Automating implementation from a PRD involves executing work based on your Product Requirements Documents or issue lists. This process enforces thorough execution by supporting TDD practices, typechecking, and full test suite execution before committing work to your branch.

Can I use test-driven development to automate PRD-based execution?▼

Yes, test-driven development is a required practice for PRD-based execution. The implementation process supports TDD where possible, allowing you to use '/tdd' for pre-agreed seams and running single test files or the full test suite.

Does automating implementation include code review and typechecking?▼

Automating implementation includes both code review and typechecking. The process ensures thorough execution by integrating regular typechecking, full test suite execution, and a '/review' step for collaborative work reviews before changes are committed.

What is the best way to execute work based on a PRD and commit it to a branch?▼

The best way to execute PRD-based work is using an automated implementation process that reads your requirements, applies TDD practices, runs typechecking and full test suites, performs a code review, and commits the completed work to your current branch.

When do I need to run the full test suite during PRD-based execution?▼

You need to run the full test suite during PRD-based execution to ensure thoroughness before committing work. The automated implementation process includes steps for regular typechecking, running single test files, and executing the full test suite.

Related Skills

Explore More Software Engineering Skills→
Lev-itLev-it

implement

Implement tasks from PRDs or issues with TDD, typechecking, and testing.

Official
Intermediate
qq824045252-ship-itqq824045252-ship-it

superpowers-finishing-a-development-branch

Integrate completed feature branches via merge, PR, keep, or discard workflows.

Community
Advanced
nseluganseluga

implement

Implement tasks from PRDs or issues with TDD and typechecking.

Community
Intermediate
SeaBrad72SeaBrad72
1

plan

Convert software design specifications into test-driven implementation plans.

Community
Advanced