Translates approved architecture designs into phased implementation plans with dependency rules.
npx skills add https://github.com/growmax/growmax-skills --skill planning-growmax
Please help me install this Agent Skill. Skill: planning Source: https://github.com/growmax/growmax-skills/tree/main/gmax/skills/planning Command: npx skills add https://github.com/growmax/growmax-skills --skill planning-growmax
void/plan/<slug>.md with a failure/edge-state table, phase DAG (depends:/shared:), and verification section inheriting the design's acceptance criteria. - Phase governance rules: Enforces one-concern-per-phase, file disjointness for parallel builds, checkable done when: criteria, and a proven-reuse rule that blocks premature abstraction. - Use Case: After an architecture design is approved, invoke this Skill to produce a phase plan where a builder can execute P1–P4 in order, knowing exactly which files each phase owns and what each phase consumes from prior phases. ## Quick Start Use the planning skill to turn the approved design at void/<task-slug>/architecture-design.md into a phase plan at void/plan/<slug>.md.High-intent search queries and answers about installing and using this skill.
Read the approved design first, then write a plan file with a failure/edge-state table and phases. Each phase lists exact files, dependencies on prior phases, and an observable done-when criterion. Never redesign the architecture inside the plan.
Assign every file to exactly one phase, keep each phase to one concern with typically five or fewer files, and order phases by project layering such as types, data access, logic, then UI. Merge tiny phases and split oversized ones.
Two phases may build in the same wave only when their file lists are disjoint and neither touches a shared file the other names. Any overlap must be resolved by ordering them with an explicit depends contract instead.
A depends entry must name what the later phase actually consumes, such as a prior phase's hook return shape, not just the phase number. This makes the contract explicit between independent builder runs.
Extraction is justified only by proven reuse: one consumer keeps code local, two or more consumers move it to the area's shared location, and universal use goes to the generic library. Premature extraction is treated as a planning defect.
avibebuilderCreate a reviewable implementation plan from repository files before coding.
Hoang604Execute PLAN.md tasks sequentially and generate a phase SUMMARY.md.
JennyfirrrDetect drift across session decisions, memories, and plan artifacts.
juanjo-zurichGenerates a combined explore, propose, and spec artifact for trivial SDD changes.