Review a Software Design Draft with Codex Forgeflow
Use Forgeflow’s read-only design reviewer to compare scope.md with design.md, flag ambiguous responsibilities and implementation risks, and record a verdict.
中文Install in Codex
Use Codex with local plugin and subagent support. Initialize Forgeflow in a project you can modify as described in the pinned repository.
- Run git clone https://github.com/sh4869221b/codex-workforge.git. From the checkout, run git checkout --detach 137e2dce2e2dbce0c44f2648ca5a1449fd39da3c.
- Follow the pinned README to load the full checkout as a local plugin. In a sample repository, run the Forgeflow bootstrap, then prepare scope and design-draft.
- Confirm the design_reviewer configuration is present, then invoke design-review. Open .codex-forgeflow/runs/<run-id>/design-review.md.
Example task
In a sample project, scope a reading list that filters by tag and shows all items when cleared. Draft a design that covers setting the filter only. Run design review and check how it records the gap.What to check
The review calls out missing clear-filter behavior and records a required revision and verdict. Look for the review file in the current run directory.
Original SKILL.md on GitHub · Updated
Frequently asked question
Why does a design review need both scope and design?
Scope defines the behavior to deliver. The design explains how it will work. Reviewing them together exposes missing behavior and unclear responsibilities.