impl-plan

Name: impl-plan
Availability: InStock
Author: polikeiji

Create implementation plan documents for architecture, data models, APIs, and tasks.

Updated Jun 5, 2026

Search Tags:#architecture #documentation #implementation planning #software development #task breakdown #technical design #data model

Ready to run

npx skills add https://github.com/polikeiji/skills --skill impl-plan-polikeiji

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: impl-plan
Source: https://github.com/polikeiji/skills/tree/main/skills/impl-plan
Command: npx skills add https://github.com/polikeiji/skills --skill impl-plan-polikeiji

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns product ideas and feature specs into clear implementation plans so teams know exactly how to build the work before coding starts.

Core Features & Use Cases

Clarifies Requirements: Identifies missing technical details before a plan is written.
Produces Structured Plan Docs: Creates focused plan files for architecture, data models, APIs, infrastructure, and tasks.
Maintains Plan Indexes: Keeps docs/plans/README.md updated as plans are added or changed.
Use Case: A developer has a new feature spec and needs a complete technical plan broken into actionable documents for the engineering team.

Quick Start

Ask the skill to convert your feature spec into an implementation plan with the right document structure, technical decisions, and task breakdown.

Frequently Asked Questions about impl-plan

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

FAQPage Schema

How do I turn feature specs into implementation plans for development teams?▼

Implementation plans transform feature specs into build-ready documents by clarifying technical requirements and structuring focused files for architecture, data models, APIs, infrastructure, and tasks before coding starts.

What should be included in technical design documents for software architecture?▼

Technical design documents should include architecture decisions, data model schemas, infrastructure requirements, API definitions, and explicit task breakdowns to guide the engineering team through implementation.

How do I break down software development tasks from a requirements document?▼

Task breakdown from requirements involves analyzing technical constraints, identifying missing details, and organizing actionable development tasks into structured plan files within a dedicated docs directory.

Can I generate data model and API documentation directly from feature specs?▼

Yes, generating data model and API documentation from feature specs involves extracting technical constraints and producing focused plan files that define schemas and endpoints for the development team.

What is the best way to maintain an index of implementation plan documents?▼

Maintaining an implementation plan index involves keeping a README file updated within the plans directory, explicitly tracking document additions, modifications, and dependencies as plans evolve.

Does implementation planning work without identifying missing technical details first?▼

Implementation planning requires identifying missing technical details before writing a plan, ensuring precise constraints are applied to architecture, data models, and infrastructure documents for accurate execution.