initializing-ledger

# Ledger Initialization

This skill creates a complete Context Ledger workspace from a project brief.

## Prerequisites

- User must provide a project brief (text description of what they're building)
- Optionally: custom path for ledger workspace (default: `./ledger/`)

## Workflow

Use TodoWrite to track these mandatory steps:

<required>
1. Parse the brief into structured components
2. Validate brief completeness (goals, constraints identifiable)
3. Create directory structure
4. Generate BRIEF.md
5. Generate PILLARS.md with default configuration
6. Confirm initialization complete
</required>

### Step 1: Parse the Brief

<good-example>
**Brief:** "Build a task management app for remote teams that integrates with Slack"
- Clear problem domain (task management)
- Specific target audience (remote teams)
- Key constraint (Slack integration)
- Can generate pillar questions immediately
</good-example>

<bad-example>
**Brief:** "Make an app"
- No problem domain specified
- No target audience
- No constraints or goals
- Cannot generate meaningful pillar questions
</bad-example>

Extract from the user's input:

| Component | Description | Required |
|-----------|-------------|----------|
| **Core idea** | What is being built (1-2 sentences) | Yes |
| **Target users** | Who will use this | Yes |
| **Key goals** | What success looks like | Yes |
| **Constraints** | What's explicitly out of scope | Recommended |
| **Context** | Any domain-specific information | Optional |

If the brief is too vague, use AskUserQuestion to clarify:

```
Question: "Your brief mentions [X] but I need more clarity on [Y]. Can you specify?"
Options:
- "[Interpretation A]"
- "[Interpretation B]"
- "Let me provide more detail"
```

### Step 2: Validate Brief Completeness

Check that the brief supports downstream work:

| Check | Pass Criteria |
|-------|---------------|
| Scope clarity | Can identify what's in/out |
| User clarity | Can describe target users |
| Goal measurability | At least one go