project-initiation

Orchestrate the sprint-planner to generate three design documents from a stakeholder specification.

1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/busboom-software-studio/design-trainer --skill project-initiation-busboom-software-studio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-initiation
Source: https://github.com/busboom-software-studio/design-trainer/tree/main/.claude/skills/project-initiation
Command: npx skills add https://github.com/busboom-software-studio/design-trainer --skill project-initiation-busboom-software-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bootstrap a new project by converting a stakeholder specification into the essential project documents: an overview, a detailed specification, and use cases.

Core Features & Use Cases

  • Automated orchestration: delegates document creation to the sprint-planner and ensures the documents exist in docs/clasi/design.
  • Guaranteed outputs: produces overview.md, specification.md, and usecases.md without manual drafting.
  • Use Case: At project kickoff when a stakeholder spec arrives, the skill begins the process and reports back the created documents.

Quick Start

Supply the stakeholder specification file path and let the sprint-planner generate the required design documents.

Frequently Asked Questions about project-initiation

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

FAQPage Schema
How do I generate project design documents from a stakeholder specification?

To initiate project documentation from a stakeholder specification, this skill orchestrates the sprint-planner to automatically draft an overview, detailed specification, and use cases directly into your docs directory.

What files are created during project initiation from a specification?

Project initiation from a specification creates three essential markdown files: docs/clasi/design/overview.md, docs/clasi/design/specification.md, and docs/clasi/design/usecases.md.

When should I use an automated project kickoff workflow?

You should use an automated project kickoff workflow when no existing design documents exist and you need to convert a newly arrived stakeholder specification into structured project documentation.

Do I need an existing docs directory to bootstrap project documents?

No existing documents are required to bootstrap project documents, but you must supply the stakeholder specification file path so the sprint-planner can write the generated outputs to the docs/clasi/design directory.

What is the best way to convert stakeholder specs into use cases and overviews?

The best way to convert stakeholder specs into use cases and overviews is using an orchestration skill that delegates drafting to a sprint-planner, ensuring guaranteed generation of overview, specification, and usecase documents.

What happens if I run project initiation when design documents already exist?

Project initiation is designed for contexts where no existing documents exist, so running it over existing files may overwrite your current overview, specification, and use cases in the docs/clasi/design directory.