implementation-plan

Name: implementation-plan
Availability: InStock
Author: ArthTech-AI

Convert approved PRDs into locked implementation plans with traceable scope.

Updated Aug 27, 2026

Search Tags:#architecture #implementation planning #feature planning #debate #prd #scope lock

Ready to run

npx skills add https://github.com/ArthTech-AI/Marketplace-extensions --skill implementation-plan-arthtech-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implementation-plan
Source: https://github.com/ArthTech-AI/Marketplace-extensions/tree/main/skills/implementation-plan
Command: npx skills add https://github.com/ArthTech-AI/Marketplace-extensions --skill implementation-plan-arthtech-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns an approved PRD into a build-ready implementation plan, helping teams lock scope, resolve feasibility concerns, and avoid vague handoff documents.

Core Features & Use Cases

PRD-to-plan conversion: Reads the feature spec, extracts user stories and edge cases, and translates them into a concrete plan.
Adversarial planning workflow: Coordinates product, architecture, and risk-review perspectives to pressure-test scope and technical approach.
Plan output and verification: Writes the final plan to the plans directory, tracks scope decisions, and supports follow-up verification and knowledge capture.
Use case: A team has already approved a feature PRD and now needs a single source of truth for what to build, how to build it, and what is explicitly out of scope.

Quick Start

Ask the implementation-plan skill to generate a locked implementation plan for a feature whose PRD is already approved.

Frequently Asked Questions about implementation-plan

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

FAQPage Schema

How do I convert an approved PRD into a build-ready implementation plan?▼

To convert an approved PRD into an implementation plan, the Skill reads feature specs from .claude/specs/<feature>.md, coordinates product and architecture debate, and writes a locked plan with traceable scope to .claude/plans/<feature>.md.

What is scope locking in feature planning and how does it prevent vague handoffs?▼

Scope locking in feature planning defines exactly what to build and what is explicitly out of scope. This prevents vague handoff documents by establishing a single source of truth for technical approach and risk decisions.

How do I resolve feasibility and technical architecture concerns during feature planning?▼

To resolve feasibility and architecture concerns during feature planning, the Skill applies an adversarial workflow that coordinates product, architecture, and risk-review perspectives to pressure-test scope and technical approach.

Can I generate implementation plans for different project sizes or complexity levels?▼

Yes, you can generate implementation plans for different complexity levels using fast, lite, and full planning modes, which adjust the depth of cost estimates, verification, and knowledge capture based on project requirements.

What do I need to start generating a locked implementation plan for my software feature?▼

To start generating a locked implementation plan, you need an approved feature PRD located at .claude/specs/<feature>.md, which the Skill reads to extract user stories, edge cases, and technical requirements.