factory-scopelisted

Writes the product scope before a project's first story — what is built, for whom, through which surfaces, how it works, how it looks — and handles the one question a delivery run may not answer for itself — a story that would need a new bounded context, a new relationship between contexts, or a surface its actor does not have yet. Use when the backlog skill reported the product scope missing, when a plan stopped with needs-human for one of those questions, when the backlog skill refused a story for a context that is not on the map, or on "/factory-scope". Produces a product scope, a decision and a map, never code.
domain-centric-development/dca-marketplace · ★ 0 · Web & Frontend · score 72

Install: claude install-skill domain-centric-development/dca-marketplace

# Answer one scoping question Input: the question — from a plan's `## needs-human`, from a story the backlog skill would not write, or from a human — plus the project's context map, its glossaries and its decision records. Output: a decision recorded where the project keeps such decisions, and the context map brought in line with it. You write no story, no plan, no test and no production code. ## First: the product scope A project's first scoping question is the whole product. When `python3 .agents/factory/story-gate.py --product` exits 3 (no product scope) or 1 (incomplete), write `backlog/product.md` — or where the profile's `product:` points — from `factory-run/templates/product.md.tmpl`, with the person who decides what is built: 1. **One question per heading, in their words.** What is built and for whom; how each actor reaches it; how it works — where state lives, what is persisted; how it looks; the qualities it needs; what it will not do. Never invent an answer: a stage that reads an invented look builds it, and a placeholder passes the gate. A heading with nothing to decide gets one honest line. 2. **Product decisions only.** "The client keeps the draft; the server stores what is submitted" belongs here; an endpoint, a package or a class does not — that is the plan stage's. 3. **Brownfield: draft from the code, ask for the rest.** Where code exists, draft `## Surfaces`, `## How it works` and `## Look and feel` from what is there — entry points, temp