quick-scope

name	quick-scope
description	Expands current-progress to final-product gaps into a multi-pass plan and closes those gaps with a fresh-context sub-agent. Use for quick-scope planning, 3-phase expansion, A to Z gap tracking, or fill-the-gap runs.

quick-scope

Use this skill to move a project from current progress to final product through two linked stages:

1. Plan expansion from a strict 3-phase outline.
2. Gap closure from [A to Z Gaps] to concrete deliverables.

When to use

• Use for: expanding a 3-phase outline into a 2-4 pass execution plan.
• Use for: producing [Completed Planned Tasks] and [A to Z Gaps].
• Use for: running a fill-the-gap pass that generates missing specs/code/tests/docs.
• Do not use for: tasks with no phase structure or no gap list.
• Do not use for: web research or guessing missing repository context.

Required input contracts

Planning input:

1. [Beginning] <Title> -- <Summary>
2. [Middle] <Title> -- <Summary>
3. [End] <Title> -- <Summary>

Optional progress snapshot:

Progress:
- Completed: <comma-separated item names or IDs>
- In progress: <item name or ID> = <NN%>

Fill-the-gap input:

• prior_output that includes [A to Z Gaps] from planning.
• Optional repo_context (files, commands, constraints).
• Optional progress_snapshot (new completion updates).

Quick start

1. Read and enforce agents/SYSTEM_PROMPT.md.
2. Run planning mode first unless a valid prior output with [A to Z Gaps] is already provided.
3. Run fill-the-gap mode to close remaining items and update status sections.
4. Repeat fill-the-gap mode as progress advances until gaps are complete.

Fresh-context sub-agent policy

Use a sub-agent with fresh context for deterministic runs.

1. Spawn sub-agent using agents/SYSTEM_PROMPT.md as its system instructions.
2. Pass one explicit mode: plan or fill-the-gap.
3. For fill-the-gap, block execution if [A to Z Gaps] is missing.
4. Keep output strict: required headers, no extra commentary.

Legacy compatibility (preserved)

• Keeps strict multi-pass planning with required ending sections.
• Keeps A-D workstream semantics (Architecture, Implementation, Surface, Validation).
• Keeps [Completed Planned Tasks] and [A to Z Gaps] as required output blocks.

Planning fallback template

If the 3-phase outline is missing or invalid, output only:

1. [Beginning] Foundation -- [core problem statement]
2. [Middle] Dual Exposure -- [main points + subpoints as needed]
3. [End] Personality + Skills + Self-Improvement Loop

Quality checks

• Planning output has Pass 1-4 headers in order (or Passes used: N first if N < 4).
• End sections are present and ordered:
  • [Completed Planned Tasks]
  • [A to Z Gaps]
• Gap percentages come only from user progress; default to 0% and round to nearest 5.
• Fill-the-gap output includes:
  • Acceptable End State (Definition)
  • Acceptable End State (Example Output)
  • Gap Fills
  • Updated Status

References

• agents/SYSTEM_PROMPT.md - canonical system prompt for both modes.
• references/examples.md - copy-paste invocation templates.