analyzing-inception-deck

Generates a project inception deck from a business architecture analysis.

Updated Dec 30, 2025
One-click install
npx skills add https://github.com/k2works/grokking-concurrency-exercise --skill analyzing-inception-deck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyzing-inception-deck
Source: https://github.com/k2works/grokking-concurrency-exercise/tree/main/.claude/skills/analyzing-inception-deck
Command: npx skills add https://github.com/k2works/grokking-concurrency-exercise --skill analyzing-inception-deck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams rapidly create an inception deck that captures why the project exists, what it will deliver, how it will be built, key risks, stakeholders, and an initial release plan, reducing misalignment at project kickoff.

Core Features & Use Cases

  • Extract and synthesize: Read a business architecture analysis and map findings to the 10-question inception deck template.
  • Structured outputs: Populate the protected 10-question template and produce a stakeholder-ready markdown inception deck including conceptual architecture and milestone guidance.
  • Visual planning: Produce PlantUML conceptual diagrams and Gantt-style milestones to illustrate architecture and release timing.
  • Use case: For a newly scoped project, generate an inception deck that defines vision, scope boundaries, prioritized features, top risks, and an MVP milestone plan for stakeholder review.

Quick Start

Read the existing business architecture analysis, answer the template's 10 questions based on that analysis, and produce the inception-deck markdown with a conceptual diagram and milestone plan.

Frequently Asked Questions about analyzing-inception-deck

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

FAQPage Schema
What is an inception deck and when do I need one for project alignment?

An inception deck is a structured document that aligns teams on project purpose, scope, stakeholders, risks, and release milestones. You need one when kicking off a newly scoped project to reduce misalignment and establish a clear vision before development begins.

How do I create an inception deck from an existing business architecture analysis?

To create an inception deck, extract information from your business architecture analysis and map the findings to a fixed 10-question template covering project purpose, scope, stakeholders, and risks. The process outputs a markdown deck with conceptual diagrams and milestone charts.

Can I use PlantUML diagrams for project milestone planning and scope visualization?

Yes, you can use PlantUML to generate conceptual architecture diagrams and Gantt-style milestone charts within your inception deck. This visual planning approach helps illustrate project scope boundaries and release timing for stakeholder review.

Do I need a completed business architecture analysis before generating an inception deck?

Yes, a completed business architecture analysis is a prerequisite. The inception deck process extracts synthesized findings from that analysis to populate project purpose, scope, risks, and initial release planning, ensuring accurate team alignment based on established business context.

What's the best way to document project risks and MVP release milestones for stakeholders?

The best way is using a structured 10-question inception deck template that captures prioritized features, top risks, and MVP milestone plans. This produces a stakeholder-ready markdown document with visual milestone guidance for immediate review.

What are the limitations of using a fixed 10-question template for project scoping?

The fixed 10-question template strictly structures project alignment documentation but cannot accommodate custom scoping frameworks or non-standard risk assessment models. It is designed for projects with existing business architecture rather than initial exploratory brainstorming sessions.