implement-plan

Execute approved technical plans from docs/plans/ and track phase completion.

349|98|Updated Feb 1, 2018
One-click install
npx skills add https://github.com/shopsys/shopsys --skill implement-plan-shopsys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-plan
Source: https://github.com/shopsys/shopsys/tree/main/.agents/skills/implement-plan
Command: npx skills add https://github.com/shopsys/shopsys --skill implement-plan-shopsys

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the implementation of approved technical plans, ensuring that project phases are completed accurately and efficiently.

Core Features & Use Cases

  • Plan Execution: Follows detailed steps outlined in plan files located in docs/plans/.
  • Progress Tracking: Updates checkboxes within plan files to mark phase completion.
  • Adaptability: Adjusts implementation based on real-world code findings while adhering to the plan's intent.
  • Use Case: A software development team has a detailed plan for refactoring a specific module. This Skill can be used to systematically implement each step of the refactoring plan, verifying changes as it progresses.

Quick Start

Use the implement-plan skill to execute the plan located at docs/plans/feature-x-refactor.md.

Frequently Asked Questions about implement-plan

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

FAQPage Schema
How do I automate project plan execution from markdown documentation?

Automating project plan execution involves reading approved technical plans from markdown files, implementing the outlined steps, and updating progress checkboxes to track phase completion accurately within your codebase.

What is the best way to track phase completion during software development workflows?

Tracking phase completion during software development is done by updating checkboxes within plan files, ensuring structured task execution and clear communication of any deviations encountered during codebase implementation.

Can I adjust implementation steps if the codebase realities differ from the technical plan?

Adjusting implementation steps for codebase realities is supported by adapting the execution based on real-world findings while strictly adhering to the original plan's intent and verifying all changes.

How do you implement technical plans when encountering unexpected codebase dependencies?

Implementing technical plans with unexpected dependencies requires deviating from the documented steps, verifying the changes made, and communicating the codebase realities clearly to maintain the plan's original intent.

Does this workflow automation require plan files to be stored in a specific directory?

Workflow automation requires plan files to be located in the docs/plans/ directory, enabling the systematic execution and progress tracking of each phase detailed within the technical documentation.