grillergeek/idd-framework

Classify terminal IDD work into a reviewable manifest, then apply explicitly approved archival with a recovery tag and reconciled ledger.

Chart a phase-zero Exploration map from confirmed destination and unresolved questions, preserving human decisions and factual research.

Review a Spec from architecture, boundary/edge and deliverable/validation perspectives with truthful parallel or sequential coverage and a consolidated report.

Define confirmed draft Expectations for an IDD Intention, with measurable criteria and at least two explicitly confirmed edge cases.

Define confirmed draft Intentions from an IDD Product, preserving purpose, priorities, dependencies and exploration lineage.

Define linked draft Intentions and Expectations together from a Product, confirming every edge case before saving the batch.

Launch the Forge web UI for this project's IDD artifacts, with literal optional port/docs arguments, an observable background process and startup error reporting.

Adversarially review one or more IDD Specs for implementation ambiguity, contradictions and unowned impact-surface files before execution. Produces finding reports and gate annotations without rewriting Spec content.

Execute one ready IDD Spec with a current clean gap-check, enforce its Boundaries, verify deliverables and produce an execution report. Use for managed Spec implementation, not general repository maintenance.

Interview stakeholders and create an IDD Product definition with business purpose, audience, owner and technical context. Use when defining a product, not when implementing a Spec.

Select and run an Intent-Driven Development workflow from product discovery through authoring, review, implementation, exploration and archival. Use when starting IDD or choosing the next IDD stage.

Author a linked draft Intention, Expectation and five-block Spec batch from a Product and confirmed feature outcome; preserve stakeholder confirmation before saving.

Claim and resolve one eligible Exploration decision, preserving unrelated staged work, human answers and truthful map completion.

Validate an implementation against every Spec Expectation, edge case, Boundary and Deliverable with actual test evidence and explicit unverified/human checks.

Review a Spec for architectural feasibility, completeness and cross-block contradictions; preserve lifecycle and content while recording current technical findings.

Create a draft five-block IDD Spec from selected Expectations with common Product context, confirmed boundaries and exact embedded edge cases.