From context-ledger
Use when starting a new product development project that needs traceable evidence and explicit decisions. Creates workspace structure from a project brief.
npx claudepluginhub synaptiai/synapti-marketplace --plugin context-ledgerThis skill uses the workspace's default tool permissions.
This skill creates a complete Context Ledger workspace from a project brief.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
This skill creates a complete Context Ledger workspace from a project brief.
./ledger/)Use TodoWrite to track these mandatory steps:
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 completeExtract 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"
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 goal is falsifiable |
| Constraint presence | At least one constraint stated |
If validation fails, prompt for missing information before proceeding.
Create the full ledger workspace. See references/pillar-definitions.md for pillar details.
mkdir -p ledger/{00-brief,01-pillars}
mkdir -p ledger/02-evidence/{market,users,tech,competitors,design,legal,ops,economics}
mkdir -p ledger/{03-synthesis,04-decisions,05-risks,06-prd,07-architecture,08-plan,09-brand,10-gtm-ops}
Write the parsed brief to 00-brief/BRIEF.md using the template in references/brief-template.md.
Critical constraints:
Create 01-pillars/PILLARS.md with:
Priority assignment logic:
Output summary:
/ledger-research)Use the AskUserQuestion tool when:
Question: "Your brief could be interpreted multiple ways. Which is closest?"
Options:
- "[Interpretation A focused on X]"
- "[Interpretation B focused on Y]"
- "Neither - let me clarify"
Question: "I couldn't identify [goals/constraints/users] from your brief. Can you specify?"
Options:
- "[Suggest likely answer based on context]"
- "[Alternative suggestion]"
- "Let me provide this information"
Question: "Based on your brief, which areas are most critical to research first?"
Options:
- "Market + Users (demand validation focus)"
- "Tech + Competitors (feasibility focus)"
- "All equally important"
- "Let me specify priorities"
Question: "Where should I create the ledger workspace?"
Options:
- "./ledger/ (current directory)" (Recommended)
- "~/projects/[project-name]/ledger/"
- "Let me specify a path"
After successful initialization:
## Ledger Initialized
**Path:** ./ledger/
**Brief:** [2-3 sentence summary]
**Pillar Priorities:**
1. [High priority pillars]
2. [Medium priority pillars]
3. [Lower priority pillars]
**Next step:** Run `/ledger-research` to begin evidence collection.