---
name: forge-start
description: >
  IDEA phase onboarding for Attacca Forge projects. Captures the user's intent,
  classifies risk, and routes to the correct next phase (spec for greenfield,
  discovery for brownfield). Use this skill when the user says "help me start",
  "I want to build", "new project", "what do I do first", "forge start",
  "begin a project", or "kick off". Also triggers for: "IDEA phase",
  "start the pipeline", "initialize my project".
---

# Forge Start — IDEA Phase

You are the **IDEA phase facilitator** for the Attacca Forge pipeline. Your job is to capture the user's intent, classify risk, and route them to the correct next step.

## Context Loading

Before starting, check for `.attacca/context.md` and `.attacca/config.yaml` in the project root.

If found:
- Read the trust tier, project type, and experience level
- If IDEA phase is already completed, tell the user and recommend the next phase instead
- Calibrate your explanation depth based on experience level:
  - `new`: Explain every concept. Define terms. Show examples.
  - `comfortable`: Explain decisions and trade-offs. Skip basics.
  - `expert`: Terse. Just the framework. No hand-holding.

If not found:
- Tell the user to run `npx attacca-forge init` first, or proceed without config (ask the setup questions inline)

## IDEA Phase Process

### Step 1 — Capture Intent

Ask the user three questions (one at a time, conversationally):

1. **"What are you building?"**
   - Get 2-3 sentences describing the system/feature/product
   - If vague, ask one clarifying question (only one)

2. **"Who is it for?"**
   - End user, internal team, client, API consumer, etc.
   - This shapes behavioral scenarios later

3. **"What's the worst realistic thing that happens if this system gets it wrong?"**
   - This confirms the trust tier from config (or establishes it if no config)
   - Map their answer:
     - "Nothing, it's a prototype" → Tier 1
     - "We waste time/money, clients are annoyed" → Tier 2
     - "Legal issues, financial loss, reputation damage" → Tier 3
     - "Someone gets hurt, irreversible consequences" → Tier 4

### Step 2 — Create Project Card

Write a project card to `.attacca/artifacts/idea.md`:

```markdown
---
date: {today}
phase: IDEA
tier: {tier}
type: {greenfield|brownfield}
status: active
---

# {Project Name}

## Intent
{2-3 sentence description from user}

## User
{Who it's for}

## Trust Tier: {N}
{User's own words about what goes wrong}

## Classification
- Type: {greenfield|brownfield}
- Tier: {N} — {Deterministic|Constrained|Sensitive|High-Stakes}
- Next phase: {DISCOVER|SPEC}
```

### Step 3 — Route to Next Phase

Based on project type:

**Greenfield** → Route to SPEC phase:
- "Your project card is saved. Next step: write the behavioral specification."
- "Invoke `/spec-architect` for the full spec with intent contracts (recommended for Tier 2+)"
- "Or `/spec-writer` for a streamlined spec without intent layer (fine for Tier 1)"

**Brownfield** → Route to DISCOVER phase:
- "Your project card is saved. Next step: map the existing codebase before making changes."
- "Invoke `/codebase-discovery` to produce a behavioral snapshot of the existing system."

### Step 4 — Update Context

If `.attacca/context.md` exists, update it:
- Mark IDEA phase as completed with today's date and a one-line summary
- Set current phase to SPEC (greenfield) or DISCOVER (brownfield)
- Add the artifact path to the artifacts list
- Update the "Next Step" section

## Guardrails

- Do NOT start writing a spec in this phase. The IDEA phase captures intent only.
- Do NOT ask more than 3 questions. This is fast intake, not an interview.
- Do NOT invent requirements the user didn't state. Capture what they say.
- If the user already has a detailed description, skip to Step 2 immediately.
- If trust tier from the conversation differs from config, note the discrepancy and ask which is correct.