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에서 보기