From bacdc95355a7d17801baf4890c45a09b98773671 Mon Sep 17 00:00:00 2001 From: GaoSSR <18220699480@163.com> Date: Sat, 19 Sep 2026 12:59:02 +0800 Subject: [PATCH 1/3] feat(schemas): open each proposal with a short review focus Closes #1908. A medium-sized change produces a proposal, design, delta specs and tasks, and reviewers either read everything or skim everything - neither catches the places where the agent guessed. A short Review Focus section right after Why gives reviewers a two-minute starting point: decisions a human should confirm, assumptions made without asking, and what is deliberately out of scope. Template and guidance change only; artifacts, validation and workflows are unchanged. Verified locally: pnpm build, pnpm test (5745 passed), pnpm exec tsc --noEmit, pnpm lint. --- schemas/spec-driven/templates/proposal.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/schemas/spec-driven/templates/proposal.md b/schemas/spec-driven/templates/proposal.md index b075f32e2a..5ed6987936 100644 --- a/schemas/spec-driven/templates/proposal.md +++ b/schemas/spec-driven/templates/proposal.md @@ -4,6 +4,13 @@ +## Review Focus + + +- Decisions a human should confirm +- Assumptions made without asking +- What is deliberately out of scope + ## What Changes From 88290450fa9bde943ff1d115b4fd8cecaf3a488f Mon Sep 17 00:00:00 2001 From: GaoSSR <18220699480@163.com> Date: Sat, 19 Sep 2026 13:00:25 +0800 Subject: [PATCH 2/3] feat(schemas): document Review Focus in the proposal instruction Pairs with the new template section so generated proposals fill it in: 3-5 bullets listing only what a reviewer should actually check - decisions a human should confirm, assumptions made without asking, deliberate exclusions. Leave empty rather than pad. --- schemas/spec-driven/schema.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/schemas/spec-driven/schema.yaml b/schemas/spec-driven/schema.yaml index 688c38a20b..94bc6c95aa 100644 --- a/schemas/spec-driven/schema.yaml +++ b/schemas/spec-driven/schema.yaml @@ -11,6 +11,7 @@ artifacts: Sections: - **Why**: 1-2 sentences on the problem or opportunity. What problem does this solve? Why now? + - **Review Focus**: 3-5 bullets listing only what a reviewer should actually check: decisions a human should confirm, assumptions made without asking, and what is deliberately out of scope. Leave empty rather than pad. - **What Changes**: Bullet list of changes. Be specific about new capabilities, modifications, or removals. Mark breaking changes with **BREAKING**. - **Capabilities**: Identify which specs will be created or modified: - **New Capabilities**: List capabilities being introduced. Each becomes a new `specs//spec.md`. Use kebab-case for path segments you introduce (e.g., `user-auth` or `identity/user-auth`) and follow the project's existing spec organization. From 220ea375132ecc1f458d081eef263a247d8c0ff9 Mon Sep 17 00:00:00 2001 From: GaoSSR <18220699480@163.com> Date: Sat, 19 Sep 2026 13:00:40 +0800 Subject: [PATCH 3/3] chore(changeset): track the proposal Review Focus change --- .changeset/soft-walls-reply.md | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 .changeset/soft-walls-reply.md diff --git a/.changeset/soft-walls-reply.md b/.changeset/soft-walls-reply.md new file mode 100644 index 0000000000..d1d62fd284 --- /dev/null +++ b/.changeset/soft-walls-reply.md @@ -0,0 +1,7 @@ +--- +"@fission-ai/openspec": patch +--- + +feat(schemas): open each proposal with a short review focus + +Adds a `## Review Focus` section to the spec-driven proposal template and a matching line in the schema instruction, so reviewers get a two-minute starting point (decisions to confirm, assumptions made without asking, deliberate exclusions) instead of reading or skimming the whole artifact set.