implement

Implement coding tasks from PRDs with TDD and typechecking.

Updated Jun 20, 2026
One-click install
npx skills add https://github.com/samuel-morrissey/skills --skill implement-samuel-morrissey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/samuel-morrissey/skills/tree/main/skills/implement
Command: npx skills add https://github.com/samuel-morrissey/skills --skill implement-samuel-morrissey

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of implementing work from Product Requirements Documents (PRDs) or issue tracking systems, enhancing productivity and consistency.

Core Features & Use Cases

  • Automated Work Implementation: Guides the implementation process, ensuring tasks are completed accurately.
  • Type-Driven Development: Encourages type-driven development practices.
  • Code Quality: Promotes regular typechecking and testing for robust code.

Quick Start

Start the implementation process by executing /tdd for type-driven development, then run /review for quality checks before committing to the branch.

Frequently Asked Questions about implement

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

FAQPage Schema
How do I implement work from a PRD while maintaining code quality?

To implement work from a PRD while maintaining code quality, you can use a guided process that encourages type-driven development and continuous testing. This approach streamlines task completion and reduces bugs by enforcing regular typechecks.

What is type-driven development and how does it help with issue implementation?

Type-driven development is a practice where type definitions guide the implementation logic. It helps with issue implementation by ensuring robust code early, reducing runtime bugs, and maintaining consistency when translating issues into code.

How do I start coding tasks from issues using continuous testing?

Start coding tasks from issues using continuous testing by executing a type-driven development command to generate initial structures, then run a quality review command to check types and tests before committing code to your branch.

Do I need a testing framework to use type-driven development for work implementation?

Yes, you need a regular testing framework to use type-driven development for work implementation. The process requires TDD practices to facilitate continuous testing and ensure robust, bug-free code throughout the development lifecycle.

What is the best way to reduce bugs during PRD implementation?

The best way to reduce bugs during PRD implementation is to adopt a workflow combining type-driven development with continuous testing. Automating regular typechecks and writing tests prior to finalizing code ensures robust outputs.

Why does continuous testing matter for type-driven development?

Continuous testing matters for type-driven development because it validates type assumptions and logic iteratively. It catches structural errors early in the implementation cycle, ensuring the final code accurately reflects the PRD requirements.