analyze

Files (1)

• SKILL.md

SKILL.md (first lines)

Analysis contract (rules + output schema) for this run:

!`cd "${CLAUDE_PLUGIN_ROOT}" && npx tsx --env-file-if-exists=.env scripts/print-analyze-contract.ts`

Produce an action plan for recording `$1`:

1. Fetch the transcript and metadata (writes `artifacts/$1.transcript.json` and `artifacts/$1.meta.json`):
   ```bash
   cd "${CLAUDE_PLUGIN_ROOT}" && npx tsx --env-file-if-exists=.env scripts/download.ts $1
   ```
2. Read `artifacts/$1.transcript.json` and `artifacts/$1.meta.json`.
3. Following the analysis contract above, produce a single action-plan JSON object. Stamp
   `recordingId`, `recordingName`, `recordingDate` from the meta file. Use only what the transcript
   supports; set owners/priority/timeframe to null when not implied, and set `ownerIsGuess` true
   for any inferred owner.
4. Write that object to `artifacts/$1.plan.json`.
5. Validate it:
   ```bash
   cd "${CLAUDE_PLUGIN_ROOT}" && npx tsx --env-file-if-exists=.env scripts/validate-plan.ts $1
   ```
   If validation fails, correct the plan and re-write it until it passes.
6. Present the plan to the user (summary, decisions, action items, open questions). Do NOT mark the
   recording processed - offer `/loom-daddy:publish $1` if they want it saved.

From fontezbrooks/loomDaddy, MIT.

More from fontezbrooks/loomDaddy