plan

Slice briefs into phased implementation plans with commit checkpoints.

Updated Nov 14, 2019
One-click install
npx skills add https://github.com/scott-rc/dotfiles --skill plan-scott-rc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/scott-rc/dotfiles/tree/main/configs/claude/skills/plan
Command: npx skills add https://github.com/scott-rc/dotfiles --skill plan-scott-rc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This setup solves the challenge of turning dense briefs or PRDs into structured, executable roadmaps by automatically deriving phased plans, recording base SHAs, and preserving a retrospective workflow.

Core Features & Use Cases

  • Create, execute, review, and retrospective planning for briefs seeded as architect briefs or PRDs.
  • Phase slicing, per-phase Type (write / test / review / benchmark / audit), and dependency enforcement to keep work green.
  • Retrospective reporting and support for Fixup or New Plan resolutions via plan review.

Quick Start

Seed a Brief into a phased plan with plan create, then run plan execute <path>.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I turn a PRD into phased implementation plans?

You can turn a PRD into phased implementation plans by seeding the brief with a create command, which slices the document into trackable phases and records the Base SHA for commit checkpoints. You then execute the plan phase-by-phase.

How does phase dependency enforcement work during plan execution?

Phase dependency enforcement keeps work green by preventing the execution of any phase until its required predecessor phases are completed. It ensures foundational tasks are resolved before dependent phases begin during phase-by-phase execution.

Can I run a retrospective workflow after executing a phased plan?

Yes, you can run a retrospective workflow after executing a phased plan. The system supports retrospective reporting and allows you to resolve open items through Fixup or New Plan resolutions during the plan review process.

What is the best way to track git commit checkpoints during feature development?

The best way to track git commit checkpoints during feature development is to derive phases from briefs and record the Base SHA. This approach orchestrates phase-by-phase execution with commit checkpoints to ensure trackable progress.

Does this planning approach support refactoring tasks or only new feature development?

This planning approach supports both refactoring tasks and new feature development. It applies to any work seeded by architect briefs or PRDs, enabling create, execute, and review flows with retrospectives for both scenarios.