kickoff-doc

Converts kickoff call transcripts into structured builder-facing reference documents.

1.4k|91|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/rjs/shaping-skills --skill kickoff-doc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kickoff-doc
Source: https://github.com/rjs/shaping-skills/tree/main/kickoff-doc
Command: npx skills add https://github.com/rjs/shaping-skills --skill kickoff-doc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Kickoff calls produce long, meandering transcripts where decisions and design details are scattered across the conversation. This Skill turns those transcripts into an organized reference document that the builder can actually use during implementation.

Core Features & Use Cases

  • Territory-based organization: Restructures sequential conversation into sections organized by areas of the system, so builders can look up how one feature works in a single place.
  • Frame and Shape structure: Captures strategic context (Problem, Outcome) separately from per-area system descriptions with inline design decisions.
  • Faithful voice preservation: Uses the actual words and reasoning from the call without adding new conclusions or editorializing beyond what was said.
  • Use Case: After a project kickoff call recorded as a VTT transcript, generate a document the implementing engineer can consult to understand what was shaped and agreed for each part of the system.

Quick Start

Turn this kickoff call transcript into a builder-facing reference document organized by system area.

Frequently Asked Questions about kickoff-doc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a kickoff meeting transcript into a project document?

Provide the full transcript (VTT or similar format) and the Skill produces a reference document with a Frame section (Problem and Outcome) and a Shape section organized by system area. Read the entire transcript first so scattered discussion of each area is consolidated.

What transcript formats does kickoff-doc support?

The Skill works with conversation transcripts including VTT files from recorded calls. Any text transcript of a kickoff conversation can serve as source material, along with optional visuals like screenshots, mockups, or breadboards from the session.

Should the kickoff document follow the order of the conversation?

No. The document is organized by territory, meaning one section per area of the system, not by the timeline of the call. Build sequences and slices are tracked separately and should not appear in this document.

Where do design decisions go in the kickoff document?

Design decisions go inline in the section of the system area they affect, not in a separate decisions section. For example, a storage choice belongs in the section about that feature so builders never cross-reference a separate list.

What are the limitations of transcript-based document generation?

The output is only as good as the input conversation; the Skill formats and distills without evaluating whether the thinking is sound. Every claim in the document must trace back to something actually said or clearly meant in the transcript.