implementation-plan

Convert high-level requirements into phased implementation plans with tasks and timelines.

3|Updated Apr 5, 2026

Search Tags:#mvp #risk-assessment #project-planning #task-breakdown #implementation-plan #definition-of-done

Ready to run

npx skills add https://github.com/dvy1987/agent-loom --skill implementation-plan-dvy1987

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implementation-plan
Source: https://github.com/dvy1987/agent-loom/tree/main/.agents/skills/implementation-plan
Command: npx skills add https://github.com/dvy1987/agent-loom --skill implementation-plan-dvy1987

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts high-level product requirements and design documents into precise, phased engineering plans that teams can execute, reducing ambiguity and planning overhead.

Core Features & Use Cases

Phase-based breakdowns: Generates Phase 0–3 plans (prereqs, MVP, refinement, testing/deployment) with concrete tasks and Definitions of Done.
Risk-aware execution: Identifies technical risks and proposes mitigations, ensuring realistic timelines and safer rollouts.
Use Case: Break down a PRD into an MVP-focused roadmap with task priorities, estimates, and verification steps ready for sprint planning.

Quick Start

Create an implementation plan for adding a new feature, include phased tasks, definitions of done, risk mitigations, timeline estimates, and save the plan to docs/plans.

Frequently Asked Questions about implementation-plan

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

FAQPage Schema

How do I turn product requirements into a phased implementation plan?▼

Implementation planning converts high-level product requirements into phased engineering plans. It breaks designs into Phase 0–3 tasks with prerequisites, definitions of done, risk mitigations, and timeline estimates ready for execution.

How do I break down a PRD for MVP scoping and sprint planning?▼

MVP scoping breaks a PRD into an MVP-focused roadmap by generating task priorities and timeline estimates. It produces core tasks, testing steps, and verification criteria structured for immediate sprint planning integration.

What is a definition of done in an engineering project plan?▼

A definition of done in an engineering plan specifies concrete completion criteria for each task. It ensures phased deliverables meet testing requirements and deployment steps before moving to the next execution phase.

How do I identify technical risks and mitigations during feature planning?▼

Risk assessment during feature planning identifies technical risks and proposes mitigations to ensure safer rollouts. It evaluates phased tasks and timeline estimates to produce realistic, risk-aware execution paths.

Can I save an implementation plan to a specific docs directory?▼

Saving an implementation plan to a docs directory is supported. You can direct the output to paths like docs/plans to store phased tasks, risk assessments, and definitions of done for project documentation.

What is the best way to structure architecture-first design tasks for a new feature?▼

Architecture-first design tasks are best structured using phased breakdowns from prerequisites to deployment. This approach generates core tasks, testing steps, and timeline estimates to convert architecture requirements into executable plans.