plan

Gather requirements interactively and produce native Tasks with DAG dependencies.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/chadananda/xswarm-tdd-claude --skill plan-chadananda
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/chadananda/xswarm-tdd-claude/tree/main/skills/plan
Command: npx skills add https://github.com/chadananda/xswarm-tdd-claude --skill plan-chadananda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning complex software work starts from unclear requirements. This Skill provides an interactive approach to capture these requirements and decompose work into a native Task DAG that can be executed in parallel.

Core Features & Use Cases

  • Interactive Phase 0: Gather requirements using 5W1H analysis, MoSCoW prioritization, Given-When-Then scenarios, and ambiguity resolution.
  • Phase 1+ Output: Produce native Tasks with DAG dependencies to enable parallel work streams and clear handoffs.
  • Phase 0 Guardrails: Require user approval before Phase 1 and enforce anti-hallucination checks to keep plans grounded.

Quick Start

Use the plan skill to begin Phase 0 by outlining the project goals, constraints, and success criteria. After user approval, Phase 1 will generate a Task DAG ready for execution.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I turn vague software requirements into an executable task DAG?

To turn vague software requirements into an executable task DAG, use an interactive Phase 0 approach that applies 5W1H analysis and MoSCoW prioritization to resolve ambiguity before generating native Tasks with dependencies.

What is the best way to decompose complex feature work for parallel execution?

The best way to decompose complex feature work for parallel execution is generating native Tasks with DAG dependencies, ensuring clear handoffs and phase gating across parallel work streams after user approval.

Can I use interactive requirement gathering for projects with ambiguous scope?

Yes, interactive requirement gathering is applicable to new features or complex projects with ambiguous scope, using Given-When-Then scenarios and ambiguity resolution to capture constraints before proceeding.

How does anti-hallucination checking work during software project planning?

Anti-hallucination checking works during software project planning by enforcing guardrails that require explicit user approval before Phase 1, ensuring generated task DAGs remain grounded in approved requirements.

When do I need phase gating in task decomposition?

You need phase gating in task decomposition when planning complex projects where work can be parallelized, requiring a strict separation between requirement gathering and native Task generation with DAG dependencies.