intent-plan

Convert approved Intents into phased TDD plans with plan.md and TASK.yaml.

15|5|Updated Jan 20, 2026

Search Tags:#automation #workflow #planning #tdd #intent #taskswarm

Ready to run

npx skills add https://github.com/ArcBlock/idd --skill intent-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: intent-plan
Source: https://github.com/ArcBlock/idd/tree/main/skills/intent-plan
Command: npx skills add https://github.com/ArcBlock/idd --skill intent-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converting a vetted Intent into a concrete, phased development plan with built-in TDD discipline, ensuring each phase is test-first and verifiable before implementation.

Core Features & Use Cases

Phase-based planning that translates Intents into ordered work items
Strict TDD workflow where tests are written before any implementation
E2E gate verification for each phase and a final plan ready for TaskSwarm execution
Generates plan.md and TASK.yaml compatible with /swarm run

Quick Start

Provide an approved INTENT.md in the intent directory and run the /intent-plan workflow to generate plan.md and its accompanying TASK.yaml.

Frequently Asked Questions about intent-plan

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

FAQPage Schema

How do I convert an approved intent into an executable development plan?▼

To convert an approved intent into a development plan, you provide an INTENT.md and run the planning workflow to decompose it into ordered, phased work items with test-first gates. This generates a plan.md and TASK.yaml for execution.

How does TDD workflow integration work when generating a phased plan?▼

TDD workflow integration enforces strict test-first discipline by requiring tests to be written and verified before any implementation begins. Each phase includes an E2E gate to ensure the plan remains verifiable throughout development.

Do I need a reviewed INTENT.md file before starting the planning workflow?▼

Yes, you need a reviewed and approved INTENT.md file placed in the intent directory before starting. The workflow relies on this vetted intent to decompose it into a structured, executable development plan.

What is the best way to structure tasks for TaskSwarm automation?▼

The best way to structure tasks for TaskSwarm automation is to generate a plan.md and its accompanying TASK.yaml. These files are specifically formatted to be compatible with the /swarm run command for automated execution.

Can I use this phased planning approach without E2E gate verification?▼

No, E2E gate verification is a built-in requirement for each phase of the generated plan. This ensures that every stage is strictly verifiable before moving forward, maintaining strict TDD discipline throughout the workflow.