/sc-context-wizard

name: sc-context-wizard
description: Interactive wizard to create context packets for agent tasks
argument-hint: "[optional: title or short description of the work]"

sc-context-wizard: Agent Context Packet Builder

_Structured workflow to create context packets that dramatically improve agent outcomes._

What is a Context Packet?

A **context packet** is a tight, structured artifact that makes implicit requirements explicit before any coding starts. Based on [Where Good Ideas Come From (for Coding Agents)](https://sunilpai.dev/posts/seven-ways/), context packets transform vague requests into agent-compatible specifications.

**The key insight**: "Agents make code cheaper. They do not make judgment cheap." The scarce skill is expressing constraints, designing verification, and maintaining feedback loops—not keystrokes.

Process:

Phase 1: Human Judgment Fields

**These require explicit user-input - the user knows these better than any agent can discover:**

1. Goal (1 sentence)

Use `AskUserQuestion` to prompt:

• **Question**: "What is the goal of this work? (1 sentence describing the outcome, not the mechanism)"
• **Examples**:
• "Make webhook ingestion reliable under variable load"
• "Add user profile editing with validation"
• "Optimize database queries for the reporting dashboard"

2. Non-Goals (Scope Boundaries)

Use `AskUserQuestion` to prompt:

• **Question**: "What are the explicit non-goals? (What's intentionally out of scope?)"
• **Examples**:
• "Not changing the webhook payload format"
• "Not building admin UI for this release"
• "Not migrating existing data"

3. Constraints (Budgets, Limits, Forbidden Actions)

Use `AskUserQuestion` to prompt:

• **Question**: "What are the constraints? (Budgets, safety properties, forbidden actions)"
• **Examples**:
• "Must complete within 200ms p95"
• "Cannot break existing API contracts"
• "No new external dependencies without approval"
• "Must maintain backward compatibility"

4. Authority Order (Source Hierarchy)

Use `AskUserQuestion` to prompt:

• **Question**: "When sources disagree, what's the authority order? (Which sources win?)"
• **Default template**: "Tests > Documentation > Code comments > Implementation"
• **Allow customization**: User can modify or accept default

Phase 2: Optional Agent-Assisted Discovery

**Leverage agents for codebase exploration:**

5. Repo Anchors (3-10 Key Files)

Use `AskUserQuestion` with two options:

• **Question**: "How should we identify repo anchors (3-10 files defining truth)?"
• **Options**:
• "Let me specify them manually" → Prompt for file paths
• "Discover them automatically" → In the BACKGROUND, spawn 1-3 **Explore agent** with prompt:

    Find 3-10 key files that define the truth for: ${goal}

    Look for:
    - Core domain models/entities
    - Primary API endpoints or controllers
    - Key configuration files
    - Main business logic files
    - Critical integration points

    Return a ranked list with brief explanations of why each file is a truth anchor.

6. Prior Art (Existing Patterns to Reuse)

Use `AskUserQuestion` with two options:

• **Question**: "How should we identify prior art (patterns to copy/reuse)?"
• **Options**:
• "Let me specify manually" → Prompt for descriptions
• "Discover automatically" → In the BACKGROUND, spawn **Explore agent** with prompt:

    Find existing patterns related to: ${goal}

    Search for:
    - Similar features or functionality
    - Comparable error handling patterns
    - Related test structures
    - Analogous validation logic
    - Existing integrations we should mirror

    Return specific file paths and pattern descriptions that should be reused.

Phase 3: Success Criteria and Risk

7. Oracle (Defining "Done")

Use `AskUserQuestion` to prompt:

• **Question**: "What's your oracle? (Tests, benchmarks, or checks that define 'done')"
• **Examples**:
• "All existing tests pass + new test suite for retries"
• "Lighthouse score > 90 on production build"
• "Benchmark shows <100ms p95 latency"
• "Manual QA checklist completed"

8. Examples (Input → Output Cases)

Use `AskUserQuestion` to prompt:

• **Question**: "Provide 2-3 examples (input → expected output, including failure cases)"
• **Format guidance**:

  Example 1 (Happy path):
  Input: [specific input]
  Output: [expected result]

  Example 2 (Edge case):
  Input: [boundary condition]
  Output: [expected behavior]

  Example 3 (Failure case):
  Input: [invalid input]
  Output: [error handling]

9. Risk and Rollout

Use `AskUserQuestion` to prompt:

• **Question**: "What are the risks and rollout considerations?"
• **Prompt for**:
• Failure modes (what could go wrong?)
• Mitigation strategies
• Deployment approach (feature flag? gradual rollout? all-at-once?)
• Rollback plan
• **Default template**: "Create a Pull Request using the pr-template. Request reviews from the engineering team. Then verify in development and/or staging before deploying to production."

Phase 4: Agent Instructions

10. Procedural Guardrails

Present this template and ask for customizations:

**Default template**:

## Agent Instructions

When implementing this work:

1. **Keep diffs small**: Aim for focused, reviewable changes
2. **Cite patterns**: Reference prior art from repo anchors explicitly
3. **Run tests frequently**: Execute oracle checks after each meaningful change
4. **Fail fast**: If assumptions break, stop and ask rather than guessing
5. **Document why**: Comments explain reasoning, not mechanics
6. **Preserve constraints**: Never violate stated constraints without explicit approval

Use `AskUserQuestion`:

• **Question**: "Review the agent instructions template. Any modifications or additions?"
• **Allow**: User can accept as-is or provide specific changes

---

Output Generation

Create the Context Packet File

**Location**: `.agen