Convert brainstormed goals into a structured plan.md with phases and dependencies.
npx skills add https://github.com/gsa9/claude-plan-skills --skill create-plan-gsa9
Please help me install this Agent Skill. Skill: create-plan Source: https://github.com/gsa9/claude-plan-skills/tree/main/skills/create-plan Command: npx skills add https://github.com/gsa9/claude-plan-skills --skill create-plan-gsa9
This Skill converts brainstormed goals into a concrete, executable plan (plan.md) that serves as the sole context bridge for subagent execution.
Use /brainstorm to clarify goals, then run /create-plan. The resulting plan.md is written to the repository root and should be executed with /exe-plan in a fresh session.
High-intent search queries and answers about installing and using this skill.
To convert brainstormed goals into an executable plan, you structure them into a concrete plan.md file. This artifact serves as the sole context bridge, featuring 3-15 discrete phases with explicit dependencies and isolation rules for fresh subagent execution.
Context isolation in multi-phase development ensures each phase runs as an isolated subagent in a fresh context. This prevents state bleed between tasks by using a self-contained plan.md artifact as the only context bridge for execution.
You structure multi-phase development plans by breaking goals into 3-15 discrete phases. The resulting plan.md defines explicit dependencies and isolation rules between phases, ensuring the repository-root artifact remains self-contained for fresh execution.
Yes, you can execute a generated plan.md in a fresh session. The plan is specifically designed to be self-contained and ready for a fresh /exe-plan session, using the repository-root artifact as the sole context bridge for subagent execution.
Yes, planning with subagents requires explicit file-path definitions. The process satisfies explicit file-path requirements and phase isolation rules, ensuring the generated plan.md artifact is self-contained and properly structured for execution.
The best way to document phases for isolated subagent execution is writing a self-contained plan.md at the repository root. It provides clear phase documentation, explicit dependencies, and isolation rules to bridge fresh execution contexts.
richardgillRefine rough ideas into designs through collaborative questioning and incremental validation.
seanGSISGDispatch parallel subagents with quality gates for decomposed plan batches.
rhys117Execute structured development plans with phase progression and Git commits.
javierhbrGenerate structured development plans with phased tasks, requirements, and QA checklists.
