draft-plan

Adversarial plan drafting uses multiple agents to critique your objective iteratively. It identifies edge cases and ambiguities, producing a structured Markdown plan file with explicit phases, work items, and acceptance criteria.

Multi-phase plan drafting with built-in quality assurance requires rigorous scrutiny across rounds. This approach enforces frontmatter and structured phases, generating a concrete artifact with dependencies and success metrics ready for execution.

Yes, drafting a plan document through this adversarial process outputs a ready-to-run Markdown file. It enforces a format compatible with run-plan, ensuring seamless integration into your project workflows.

Yes, adversarial plan drafting is designed specifically for complex projects requiring rigorous scrutiny. Multiple agents converge on a robust plan by challenging assumptions, resolving risks, and refining ambiguities across iterative critique rounds.

Adversarial review is needed when drafting plans for complex projects where edge cases and risks are critical. It moves beyond simple task lists by applying multi-round critique to forge an airtight plan document.

Generating plan files through iterative critique requires defining a clear plan objective and output path upfront. It focuses on producing a structured Markdown artifact, meaning it serves planning phases rather than direct code execution.