dreambound/plan-refiner-skill

Overview

This skill generates and iteratively refines implementation plans from an initial specification or prompt. It creates an initial plan and runs a minimum of three parallel review passes using fresh agent contexts, surfacing assumptions, issues, and an audit trail. Users can continue passes until they are satisfied and receive a final plan, accumulated clarifications, and a complete pass history.

How this skill works

Provide an initial spec (file path or text). The skill writes an initial plan and then runs parallel review agents each pass: a standard reviewer (spec alignment and completeness), an adversarial reviewer (assumptions and failure modes), and an optional custom reviewer. Feedback is merged by an update agent into plan.md, recorded in an audit folder, and presented to the user along with any skipped verification notes (e.g., if version-check tools are unavailable).

When to use it

• Turning rough requirements into a step-by-step implementation plan
• Validating assumptions, versions, and failure modes before engineering work begins
• Producing a traceable audit trail of design decisions and review feedback
• Onboarding teams with a polished plan and clarifications document
• When you need multi-perspective review without manual coordination

Best practices

• Provide a clear initial_spec.md or a concise prompt as the source of truth
• Enable a custom reviewer when you need specialist focus (security, performance, compliance)
• Preserve the original spec: all reviewers must re-read initial_spec.md to avoid drift
• Review at least three passes, then continue until the plan meets acceptance criteria
• Use the audit/ directory to inspect historical plan versions and changelogs

Example use cases

• Convert a product requirements document into a developer-ready implementation plan with milestones
• Refine a CI/CD workflow spec, ensuring tool versions and APIs are current
• Prepare a security-sensitive feature by adding an adversarial reviewer to surface attack vectors
• Iteratively shape a migration plan with traceable assumptions and rollback steps
• Produce a final plan and clarifications for handoff to an engineering squad