project-initiation
Bootstrap a new project from a stakeholder's specification — produces overview, specification, and use cases
- License 许可
- MIT
- 最近更新
- 2026-09-25
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- project-initiation
- description
- Bootstrap a new project from a stakeholder's specification — produces overview, specification, and use cases
03 SKILL.md 正文
Project Initiation Skill
Process a written specification into structured project documents that all other processes will reference throughout the project lifecycle.
When to Use
At the start of a new project when the stakeholder has provided a
written specification. There are no existing overview.md,
specification.md, or usecases.md documents yet.
Inputs
- A path to a written specification file from the stakeholder
Process
-
Resolve the project's configured design directory. Read
paths.designfrom thepaths:map in.clasi/config.yaml. If.clasi/config.yamlis absent, or has nodesignentry underpaths:, the default isdocs/design/. Do not assume.clasi/design/— that is not the default and is wrong for most projects; a write there leavesoverview_exists()(which checksdesign_dir/overview.md) permanently unable to see the result, and theinitializetransition stays blocked regardless. -
Dispatch to the sprint-planner agent via the Agent tool with:
- The specification file path
- The resolved design directory path (from step 1)
- Instruction to write all three documents there
The sprint-planner agent writes all three documents. Do not write them yourself.
-
Await completion. The sprint-planner returns when all three documents are written.
-
Report the result to the stakeholder — confirm the files created and any key decisions made.
Documents the Sprint-Planner Produces
All three documents are written to the project's configured design
directory (resolved in step 1 above — paths.design in
.clasi/config.yaml, default docs/design/):
overview.md — A one-page summary of the
project. An elevator pitch for quick context. It is additive, NOT a
replacement for the specification.
specification.md — The full feature
specification, preserving ALL stakeholder detail. Exact messages,
behavior rules, edge cases, test expectations — if the stakeholder
wrote it, it MUST survive. Reorganize for clarity, but do not lose
information. Do not summarize, paraphrase, or omit.
usecases.md — Numbered use cases (UC-001,
UC-002, etc.) extracted from the specification. Each use case has: ID,
title, actor, preconditions, main flow, postconditions, and error flows.
Critical Rule
Do not write documents yourself. Dispatch to the sprint-planner agent. Your role is orchestration, not authorship.
Output
Three documents in the project's configured design directory (default
docs/design/; see paths.design in .clasi/config.yaml):
overview.md, specification.md, usecases.md.