implementation-planner

Name: implementation-planner
Availability: InStock
Author: ylxmf

Generate a verifiable Implementation Story Spec from approved requirements and design.

11|1|Updated Mar 3, 2026

Search Tags:#planning #handoff #traceability #risk-management #requirements-to-design #implementation-story

Ready to run

npx skills add https://github.com/ylxmf2005/AgentCorp --skill implementation-planner-ylxmf2005

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implementation-planner
Source: https://github.com/ylxmf2005/AgentCorp/tree/main/agentcorp/implementation-planner
Command: npx skills add https://github.com/ylxmf2005/AgentCorp --skill implementation-planner-ylxmf2005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill mediates the handoff between approved requirements and engineering delivery by producing a precise, bounded Implementation Story Spec, preventing scope creep and ensuring design intent is preserved during planning.

Core Features & Use Cases

Slice approved designs into ordered, independently verifiable stories with clear boundaries and landing points.
Enforce plan discipline by cross-checking requirements, test plans, and design artifacts; block when gaps exist.
Generate a ready-for-plan-review Implementation Story Spec with source context, acceptance criteria, tasks, constraints, and verification guidance.

Quick Start

Provide an Implementation Story Spec by feeding the approved requirements and design artifacts through the planner to generate the ready-for-plan-review document.

Frequently Asked Questions about implementation-planner

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

FAQPage Schema

How do I turn approved requirements and design into actionable implementation stories?▼

To turn approved requirements and design into implementation stories, you feed the artifacts through a planner to generate a verifiable Implementation Story Spec with slice-by-slice tasks, acceptance criteria, and source context.

What is the best way to prevent scope creep during the design handoff to engineering?▼

To prevent scope creep during design handoff, you produce a bounded Implementation Story Spec that enforces plan discipline by cross-checking requirements and design artifacts to ensure clear story boundaries.

How does cross-checking requirements and test plans ensure plan readiness for engineers?▼

Cross-checking requirements and test plans ensures plan readiness by enforcing plan discipline; the process blocks handoff when gaps exist between the design artifacts and test plans, ensuring verifiable tasks.

Can I slice a large software design into independently verifiable engineering tasks?▼

Yes, you can slice a large software design into independently verifiable engineering tasks by generating an Implementation Story Spec that produces ordered stories with clear boundaries and landing points.

What constraints and verification guidance are included in an implementation story spec?▼

An implementation story spec includes source context, explicit constraints, and verification guidance alongside acceptance criteria, ensuring formal handoff documentation and traceability to the original requirements.

Why does the implementation planning process block when gaps exist between requirements and design?▼

The implementation planning process blocks when gaps exist between requirements and design to enforce plan discipline, preventing scope creep and ensuring design intent is fully preserved before engineering delivery begins.