Transforms implementation requests into phased technical specifications with approval gates and backlog routing.
npx skills add https://github.com/zoraxl/team-brain --skill planning-zoraxl
Please help me install this Agent Skill. Skill: planning Source: https://github.com/zoraxl/team-brain/tree/main/.cursor/skills/planning Command: npx skills add https://github.com/zoraxl/team-brain --skill planning-zoraxl
This skill solves the ambiguity and lack of structure in the early stages of software development by enforcing a rigorous, multi-phase planning process that prevents premature coding and ensures team alignment.
Ask the agent to plan the implementation of the new authentication module based on the existing brainstorm document.
High-intent search queries and answers about installing and using this skill.
Structuring technical specifications requires decomposing high-level feature requests into shippable phases. The planning skill enforces a multi-phase lifecycle with mandatory approval gates, resolving open questions and routing backlog items before any coding begins.
Preventing premature coding requires strict lifecycle management and approval gates. This enforces a mandatory pause for user confirmation before technical specifications are written, ensuring team alignment and resolving open questions before development starts.
Breaking down software architecture into shippable units involves automated phase decomposition. The planning process transforms implementation intents into independent technical phases, tracking workflow states from initial brainstorm to ready-to-ship.
The technical specification process explicitly supports routing unresolved open questions to a backlog. Lifecycle management tracks work states from brainstorm to ready-to-ship, ensuring all open questions are resolved or formally deferred.
You can enforce mandatory review gates before writing implementation specs. The planning lifecycle requires explicit user confirmation pauses, ensuring technical specifications are only generated after formal approval is granted.
A strict lifecycle state machine for feature planning should not be used when rapid prototyping is needed without formal documentation. The rigorous multi-phase enforcement and approval gates are designed to prevent ambiguity, making it unsuitable for unstructured exploratory coding.
ccstudentccGenerate executable implementation plans with task decomposition, file mapping, and test plans.
darelabs-techGenerate structured technical blueprints with data models, API endpoints, and security protocols.
shaul1991Scan project roots to generate lifecycle status dashboards with ALM governance.
pythonValidate PO file translations for terminology, punctuation, and reST syntax.
