brainstorm-task

Plan and track implementation work with traceability to the code graph.

8|3|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/demon24ru/code-review-graph --skill brainstorm-task
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorm-task
Source: https://github.com/demon24ru/code-review-graph/tree/main/skills/brainstorm-task
Command: npx skills add https://github.com/demon24ru/code-review-graph --skill brainstorm-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan and track implementation work with full traceability to the code graph.

Core Features & Use Cases

  • Single-Pipeline Discipline: One root task at a time; call task_get_active_root to ensure idle before creating a new root.
  • Phase-driven workflow: Brainstorm, Validate, Implement, Close — with atomic batch creation and clear handoffs.
  • Structured decomposition: Decompose work into a 3–8 node leaf task per feature and wire dependencies and contracts as needed.
  • Handoff-ready context: Exports task structure, notes, and code refs for designer and coder handoffs.

Quick Start

Create a root task and decompose into subtasks in batch mode, then wire dependencies atomically to maintain a clean, auditable pipeline.

Frequently Asked Questions about brainstorm-task

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decompose a project into a task DAG with dependency wiring?

To decompose a project into a task DAG, create a root task and break it into 3–8 leaf subtasks in batch mode, then wire dependencies atomically to maintain a clean, auditable pipeline.

What is single-pipeline discipline in task management?

Single-pipeline discipline in task management enforces having only one active root task at a time, requiring you to ensure the pipeline is idle before creating a new root.

How do I generate handoff context for a development task?

You generate handoff context by exporting the task DAG structure, notes, and code references, producing ready context for designer and coder handoffs.

What phases does the task planning workflow follow from brainstorm to handoff?

The task planning workflow follows four phases: Brainstorm, Validate, Implement, and Close, ensuring atomic batch creation and clear handoffs across the product development cycle.

Can I track multiple root tasks simultaneously in a task DAG?

No, you cannot track multiple root tasks simultaneously. The system enforces single-pipeline discipline, requiring you to check for an active root and ensure it is idle before creating a new one.