Menu
Turn a shaped project kickoff transcript into a builder-facing reference document organized by system territory.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | kickoff-doc |
| description | Turn a shaped project kickoff transcript into a builder-facing reference document organized by system territory. |
| user-invocable | true |
| argument-hint | [kickoff transcript, notes, visuals, mockups, or breadboards] |
Use this skill when the user has a kickoff transcript, VTT file, call notes, visuals, mockups, or breadboards and wants a reference document for the person who will build the shaped work.
This is a Codex-safe adaptation of the upstream kickoff-doc shaping skill. It has no external command, model, deployment, credential, or network dependency.
Establish:
If the source material may contain RED data, keep processing local-only and do not persist raw excerpts outside the target document.
Organize by territory, not timeline.
A kickoff transcript is sequential. People circle back, branch, and mention details out of order. The document should reconstruct the system areas being described, so a builder can look up one area and see the relevant behavior, affordances, decisions, and caveats together.
Do not organize by build sequence. If the team identified implementation slices, those belong in a separate slices or implementation plan document.
Produce:
---
shaping: true
---
# [Project] - Kickoff Reference
## Frame
### Problem
[Why this project, why now, what is broken or missing.]
### Outcome
[The specific outcomes expected.]
## Shape
### [System Area]
[What this area is, what is on screen or in the system, and how it behaves.]
[Inline design decisions and edge cases that belong to this area.]
Under ## Shape, create one ### section per system area. For each area, capture:
The document records shared understanding from the kickoff.
Do:
Avoid:
For every claim, identify one of:
If a claim has none of those, remove it or turn it into an open question.
Improve, audit, simplify, rewrite, or migrate prompts, tool descriptions, agent instructions, and prompt stacks for GPT-5.6 Sol or the GPT-5.6 family. Use for outcome-first prompt design, autonomy boundaries, tool routing, PTC, grounding, verbosity, reasoning effort, and prompt evals.
Apply a deep, design-minded engineering workflow for complex work that needs careful planning, iteration, and simplification.
Use when preparing or running a Claude CLI agentic engineering review through claude -p for repository audits, architecture analysis, system design, security review, large refactors, specs, RFCs, or evidence-grounded long-form engineering analysis.
Use when preparing or running a ZCode GLM-5.2 agentic builder workflow through zcode --prompt for fast implementation, iterative code generation, focused fixes, and validation on an existing repository.
Apply adversarial opposite-analysis to plans, specs, architecture, code changes, and claims. Use when the user asks for adversarial review, opposing analysis, contrarian review, red-team reasoning, or Z.ai and MiniMax cross-checks through the Ralph MCP router.
Review and adjudicate Bugbot, Cursor, Seer, and similar automated PR feedback with local evidence before accepting, fixing, or dismissing findings.