Convert design documents into implementation plans with task breakdowns and progress tracking.
npx skills add https://github.com/tacogips/git-xnotes --skill impl-plan
Please help me install this Agent Skill. Skill: impl-plan Source: https://github.com/tacogips/git-xnotes/tree/main/.claude/skills/impl-plan Command: npx skills add https://github.com/tacogips/git-xnotes --skill impl-plan
The Implementation Plan Skill bridges design documents and executable work by providing a structured approach to craft actionable implementation plans, ensuring clarity and alignment across design, development, and delivery.
Draft a new implementation plan from a design document by filling the header, listing modules, and establishing initial progress tracking.
High-intent search queries and answers about installing and using this skill.
To convert a design document into an implementation plan, you translate the design into granular task breakdowns. This involves defining scope with 1-3 sessions, assigning 3-10 subtasks for parallel work, and establishing initial progress tracking.
The best way to track progress across iterations is by using a standardized file layout with a PROGRESS.json tracker. This enforces plan structure and task granularity rules while maintaining frontmatter metadata for collaboration and auditing.
You structure an implementation plan for parallel execution by defining scope with 1-3 sessions and breaking work into 3-10 subtasks. A clear header, design references, and progress-tracking sections maintain alignment across development.
Yes, you need Markdown and frontmatter metadata for design-to-plan task management. Maintaining frontmatter metadata and a consistent plan layout under a prescribed directory structure supports collaboration, progress tracking, and workflow auditing.
Yes, you can govern implementation plan templates using a standard file layout. This approach enforces a structured directory for plans, utilizes a PROGRESS.json tracker, and applies prescribed sections to guide multi-session development.
You should avoid a frontmatter-based model for task breakdowns if your project requires real-time progress syncing rather than file-based tracking, or if your development workflow operates outside structured Markdown documentation and prescribed directory layouts.
PiaoxuemoliGenerate markdown planning documents from user input without execution.
max8989Track feature work by managing subtasks and dependencies via a CLI.
jleechanorgBuild and maintain an interlinked Markdown knowledge base with provenance tracking.
l395624064Automate requirements, design, and task planning workflows with EARS syntax.
