Write a Testable Project Scope with Codex Forgeflow

Turn a raw request into a Forgeflow scope document that defines the goal, constraints, assumptions, and affected areas. Keep delivery-changing ambiguities visible.

中文

Install in Codex

Use Codex with local plugin support. Initialize Forgeflow in a sample repository you can modify.

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. Run the Forgeflow bootstrap in a sample project.
Invoke scope for the new run and supply the sample request and constraints. Review .codex-forgeflow/runs/<run-id>/scope.md.

Example task

In a local sample project, ask to make reports downloadable. Specify CSV only for this release and an entry on the report list. Ask the skill to flag the unspecified export columns.

What to check

The scope identifies CSV and the report list as established, names affected areas, and lists the columns as unresolved. Keep critical ambiguity visible in the draft or as an open issue.

Original SKILL.md on GitHub · Updated 2026-11-11

Frequently asked question

Where should future PDF support go?

List it as deferred or out of scope according to the product decision. The current release and its acceptance criteria cover the confirmed CSV behavior.