skills/fenrick/consulting-workflows/report-storyboard-builder

report-storyboard-builder

SKILL.md

Report Storyboard Builder

Use this skill to create the written report skeleton before detailed prose.

Bundled materials

Read in this order:

  1. references/workflow.md
  2. references/validation-checklist.md
  3. references/quality-standard.md
  4. references/term-sheet.md
  5. references/repo-map.md
  6. references/tracking-readme.md
  7. assets/templates/report-storyboard-template.md
  8. assets/templates/section-file-plan-template.md
  9. assets/templates/open-questions-template.md

Inputs

  • tracking/storyline-architecture.md
  • tracking/source-register.md
  • tracking/review-notebook.md
  • project brief and key processed inputs

Core outcome

Produce a report storyboard that tells writers exactly what each section must do.

Required outputs

  1. tracking/report-storyboard.md
  2. section file plan for report-body/ (ordered list with expected file names)
  3. tracking/open-questions.md updates for sections lacking evidence

Quality gate

Apply references/quality-standard.md before finalizing outputs.

Working materials discipline

  • keep section logic in tracking/report-storyboard.md
  • keep unresolved evidence gaps in tracking/open-questions.md
  • keep assumptions explicit in section-level notes
  • build the artifact through section skeleton, section bullets, short notes, and flow passes

Back-iteration loop

  1. build first-pass section storyboard
  2. check section claims against storyline and source register
  3. tighten overlaps, remove orphan sections, and re-sequence
  4. refresh outputs and unresolved items before handoff

Storyboard contract

For each planned section:

  • section title
  • section purpose
  • key claim(s)
  • required evidence
  • practical implication
  • what not to include
  • dependencies on other sections

Include:

  • recommended drafting order
  • minimum front-end requirements (executive summary, introduction)
  • appendix candidates and rationale

Quality rules

  • Keep sections decision-relevant and non-overlapping.
  • Tie each section to at least one evidence source or explicit evidence gap.
  • Prevent orphan sections that cannot be proven from current inputs.

Do not

  • write full polished prose
  • create section headings without a proof obligation
  • duplicate storyline content without adaptation for written narrative
Weekly Installs
3
First Seen
5 days ago
Installed on
opencode3
gemini-cli3
github-copilot3
codex3
kimi-cli3
amp3