feat(schemas): open each proposal with a short review focus

.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.

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/<capability-path>/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.

schemas/spec-driven/templates/proposal.md

@@ -4,6 +4,13 @@
 
 <!-- Explain the motivation for this change. What problem does this solve? Why now? -->
 
+## Review Focus
+
+<!-- 3-5 bullets. Leave empty rather than pad. -->
+- Decisions a human should confirm
+- Assumptions made without asking
+- What is deliberately out of scope
+
 ## What Changes
 
 <!-- Describe what will change. Be specific about new capabilities, modifications, or removals. -->