Skip to main content

shaping-kickoff

Turn kickoff transcripts into a builder-facing territory map before carding. Use when kickoff conversations are rich but implementation slices are not yet legible.

跳到安装

来源信息

仓库
hashintel/labs
最近来源活动
2026年3月23日 12:12
检测到的 SKILL.md 语言
英语
星标
36
分支
14

安装方式

默认使用会先检查来源的 Prompt;你也可以切换为直接命令,或下载本地副本。

检查来源文件

决定是否安装前,请先阅读 SKILL.md,以及 SkillsMP 当前展示的配套文件。

正在显示 SKILL.md

SKILL.md
来源说明 · 只读预览
name
shaping-kickoff
description
Turn kickoff transcripts into a builder-facing territory map before carding. Use when kickoff conversations are rich but implementation slices are not yet legible.
argument-hint
[kickoff transcript paths and project topic]
# Shape Kickoff (Adjunct) Convert kickoff conversation timelines into a territory-oriented artifact that can feed pragma planning. ## Source And Adaptation Note Adopted from `rjs/shaping-skills` (`kickoff-doc`) and adapted for this repository. Modifications: - Namespaced as `pragma:shaping-*` - Explicit handoff into `pragma:*` - Guardrails against replacing capsule/card authority ## When To Use - The team has a kickoff transcript that contains decisions across many topics - The builder needs a coherent map by system area, not by conversation order - You need a reliable planning handoff artifact before card creation ## Procedure 1. Read the full kickoff source before writing. 2. Organize by territory (system area), not timeline. 3. Capture decision rationale where each decision matters. 4. Separate provisional choices from committed boundaries. 5. Produce pragma handoff notes. ## Required Output ```md ## Kickoff Territory Map [organized by system area with key decisions inline] ## Handoff To Pragma - Capsule impacts: [terminology/invariant updates] - Candidate cards: [specific vertical behaviors] - Validation risk: [items requiring `/pragma:spike` or `/pragma:characterize`] - Next command: [`/pragma:card` by default] ``` ## Constraints - Do not output implementation sequencing as an alternative planning system. - Do not redefine glossary terms outside the capsule. - Do not bypass `/pragma:card`. ## Lifecycle - **State**: `planning` - **Next**: `/pragma:card` - **Loop**: `/pragma:consult`
在 GitHub 查看