Enforce goal-backward planning and quality gates in /st:plan and /st:phase-plan workflows.
npx skills add https://github.com/tuanldas/superteam --skill plan-quality
Please help me install this Agent Skill. Skill: plan-quality Source: https://github.com/tuanldas/superteam/tree/main/skills/plan-quality Command: npx skills add https://github.com/tuanldas/superteam --skill plan-quality
Plan-quality enforces backward design and strict quality gates to ensure every plan is concrete, testable, and executable, reducing ambiguity and rework.
/st:plan, /st:phase-plan, and related agents like plan-checker, TDD discipline, and verification.Create a plan using /st:plan for a defined goal and enable the plan-checker workflow to validate quality gates.
High-intent search queries and answers about installing and using this skill.
Goal-backward planning derives must-haves and artifacts from a single observable outcome, ensuring every plan is concrete, testable, and executable. It enforces 3-7 must-haves, exact file paths, and acceptance criteria to eliminate ambiguity before execution begins.
Create a phase-level plan using the phase-plan workflow to derive must-haves and artifacts from a defined goal, then validate them through a plan-checker protocol that enforces exact file paths, read-first requirements, and acceptance criteria for verifiable execution.
The best way to reduce ambiguity and rework is to enforce strict quality gates and backward design, deriving 3-7 must-haves and acceptance criteria from a single observable outcome to ensure plans are concrete and testable before development starts.
Goal-backward planning integrates with TDD discipline and verification workflows by imposing must-haves, exact file paths, and a plan-checker protocol, aligning plan creation with downstream testing and artifact validation seamlessly.
Yes, the plan-checker protocol validates task-level plans by enforcing exact file paths, read-first directives, and 3-7 must-haves, ensuring plans meet strict quality gates and are fully executable without open questions.
Goal-backward design should not be used when a single observable outcome cannot be clearly defined, as the framework relies on deriving 3-7 must-haves, exact file paths, and acceptance criteria strictly from that one concrete goal to ensure verifiable execution.
LuuKhoaHocGenerate executable phase plans with task decomposition and dependency graphs.
dailydmTranslate breakdown tasks into implementation plans and code changes.
unheadedDetect and enforce battle plan execution discipline across timelines and verification gates.
nickthelegendGenerate executable phase plans with dependency graphs and goal-backward verification.