Transform ambiguous requirements into constraint-bound implementation plans with ECL documents.
npx skills add https://github.com/TzJ2006/gadget --skill ccplan
Please help me install this Agent Skill. Skill: ccplan Source: https://github.com/TzJ2006/gadget/tree/main/skills/ccplan Command: npx skills add https://github.com/TzJ2006/gadget --skill ccplan
Diverge-then-converge requirement engineering with prompt calibration, adversarial validation, feasibility probing, and an Evolving Constraint Language (ECL) that persists decisions across sessions and models. Replaces linear planning with a spiral: calibrate → hypothesize → challenge → diverge → converge → probe → confront → review → implement → loop.
Run /ccplan with your feature request to begin Phase 0 calibration and let the spiral planning workflow guide you through to implementation.
High-intent search queries and answers about installing and using this skill.
Planning for ambiguous requirements uses a phase-driven diverge-then-converge workflow. It transforms vague requests into constraint-bound implementation plans through prompt calibration, hypothesis interrogation, and feasibility probing.
Adversarial validation in requirement engineering is a mechanism that challenges hypotheses during the planning workflow. It filters divergent ideas by interrogating feasibility before converging into a formal implementation plan.
To persist planning decisions across multiple AI sessions, use an Evolving Constraint Language (ECL) document. ECL stores constraint-bound decisions, allowing implementation plans to survive across different sessions and models.
Yes, you can enforce a review gate before feature implementation. The phase-driven workflow automatically escalates to a formal Review Gate, generating feature guards to prevent regressions before implementation begins.
Linear planning is replaced by a spiral workflow for complex architectural choices. This approach cycles through calibration, hypothesis interrogation, and adversarial filtering to handle ambiguity better than linear methods.
alextangsonConfigure brand positioning and writing style through a five-phase setup workflow.
jineyneGenerate implementation plans and design artifacts from spec-kit repositories.
Clay-HHKGuide researchers through structured ideation frameworks to discover research directions.
phillippelevidadDesign scalable distributed systems and document architectural decisions with ADRs.
