journal-creator
Journal Creator — Story Journal
Purpose
Read validated specification documents and produce one deliverable:
docs/planning/journal.md— Dependency-ordered journal of user and technical stories
The journal creator's primary value is bridging specs to implementation — transforming validated requirements, architecture decisions, and design specifications into an actionable, ordered backlog where every story traces to its source, every dependency is explicit, and every parallel opportunity is surfaced. If a requirement isn't captured in a story, it will be lost in implementation.
Journal Creator Mindset
Embody these qualities throughout the process:
- Completeness obsession — if a requirement isn't captured in a story, it will be lost in implementation. Every FR, every architecturally-significant NFR, every ADR must have a home.
- Dependency precision — incorrect ordering wastes parallel capacity or causes blocked work. Dependencies must be genuine (data/API/infrastructure), not assumed.
- Traceability discipline — every story must trace back to its source requirements and architecture decisions so downstream phases can work without re-reading all specs.
More from raffaelecamanzo/skills
marp-deck-visual-designer
Transform a MARP presentation plan into concrete visual and layout decisions, including generating Mermaid diagrams when explicitly planned. Use only when a deck-plan.md already exists.
33marp-deck-gen
Generate the final MARP deck markdown from definition, deck plan, and visual design artifacts, applying deck-template layout rules deterministically. Use only when all three source artifacts exist.
29marp-deck-planner
Plan a MARP presentation from a high-level deck definition (sections, key messages, constraints). Transform raw content into a structured, impactful presentation plan with refined messaging and professional framing.
27marp-deck-workflow
Interactive presentation consultant that guides users through planning, visual design, and generation consultations before delegating to sub-skills. Single entry point for the full MARP deck pipeline with 3 consultation rounds and visual QA.
27marp-deck-checker
Visual QA on the rendered PDF of a MARP deck. Reads every slide page-by-page, detects rendering and layout flaws visible only in the final output, and directly invokes marp-deck-gen with a surgical fix prompt when flaws are found. No report file is written.
22business-analyst
Analyze a user request document and produce a Functional Requirements Specification (FRS) and User Acceptance Test (UAT) cases. Use when the user asks to analyze requirements, extract functional requirements, create acceptance tests, write FRS/UAT documents, or references docs/specs/requests. Can be invoked standalone or by the product-owner skill with a file argument. The analyst challenges the user with probing questions to surface gaps, implicit assumptions, and missing edge cases before producing analyst-frs.md and analyst-UAT.md at docs/specs/.
7