Skip to main content

Turn an idea into a sequenced backlog.

What Kickstart does

Kickstart turns a fresh project idea into a sequenced consumer guide — a single Markdown document with 6 to 10 seed features ordered by dependency, each ready to feed into the rest of the lifecycle. Run it before you have a backlog. The skill walks through three stages: it captures the idea, picks a technology stack, and writes the guide. The output is a real document you can hand to a teammate or paste into Discover.

  1. Idea Intake

    Capture the project idea, target user, and key capabilities through structured prompts.

  2. Stack Selection

    Detect an active stack pack or guide the developer to select or describe a stack.

  3. Guide Generation

    Produce a consumer guide with setup phases, a feature summary table, and per-feature seed blocks ordered for incremental value delivery.

Kickstart or Discover?

KickstartDiscover
When to useIdea-stage. No backlog yet.Feature-stage. Backlog exists.
What each producesConsumer guide with 6 to 10 sequenced seed features.One GitHub Issue scored and validated.
Project state requiredEmpty repo or fresh idea.Existing project with a backlog convention.
Number of features per run6 to 10 features in one pass.One feature per invocation.
Next-step semanticFeed seeds into Discover.Run Define to author the PRD.

What Kickstart produces

Three abbreviated seed-feature blocks from a real consumer guide — same shape, same headings, same sequencing. Annotations name the contract each block carries.

#### F-001: Project Scaffold & Design System

**Goal**: Establish the Next.js project structure, shared Tailwind design tokens, dark/light theme system aligned with davidmatousek.com branding, and a single source of truth for canonical external URLs.

**Stories**: 5 stories covering static-export config, Tailwind brand-token preset, dark-mode default with persistence, base layout primitives, and the `lib/site-config.ts` constants module.

**Interface Contract**: Tailwind preset file, theme provider component, `<Section>` layout component, `lib/site-config.ts`, static-export build pipeline.

**Definition of Done**: `npm run build` produces a static `out/` directory, banned fonts absent from primary stack, dark/light toggle persists across reloads, `<Section>` renders correctly at 320 / 768 / 1024 / 1440 px.
Feature ID and one-line title. The ID is sequential across the guide; the title names the surface the feature ships.One declarative sentence framing the user outcome. Answers “what will exist after this feature ships?” in concrete terms.User stories with explicit acceptance criteria. Each story is independently demonstrable and scoped to a small, verifiable slice.Constraints that apply across every story in the feature — accessibility, responsive breakpoints, performance budgets, keyboard navigation.Named outputs the feature produces — routes, components, exports, build pipelines — for downstream features to consume.The merge bar. Concrete, verifiable checks the feature must pass before the branch ships and the issue closes.
#### F-005: How It Works Page

**Goal**: Provide a deep-dive into the ADLC lifecycle, Governance Triad, and three conceptual frameworks (Maturity Ladder, VOICE Principles, Four Pillars) for visitors who want to understand the methodology.

**Stories**: 5 stories covering the ADLC walkthrough, the Triad table, the Maturity Ladder rungs, the VOICE Principles mnemonic, and the Four Pillars OOP-to-AOD mapping.

**Interface Contract**: Page route `app/how-it-works/page.tsx`, reusable `StageCard` component, deep-link anchors per framework section.

**Definition of Done**: Page covers all five framework sections, every section has a stable anchor ID, every concept link routes to an on-site chapter, cross-cutting ACs (responsive, keyboard nav, Lighthouse ≥ 90) verified.
#### F-006: Getting Started Page

**Goal**: Provide a clear installation and first-workflow guide so visitors can go from zero to their first AOD lifecycle run within a 30-minute timebox.

**Stories**: 3 stories covering the prerequisites checklist, the step-by-step install commands, and the first-workflow walkthrough.

**Interface Contract**: Page route `app/getting-started/page.tsx`, reuses the `CopyButton` primitive from F-011a.

**Definition of Done**: A reader from a clean machine can clone → init → run their first `/aod.discover → /aod.deliver` cycle in ≤ 30 minutes, every code block has a working CopyButton, cross-cutting ACs verified.
Features are ordered Foundation → Core → User-Facing → Polish. Each feature depends only on features earlier in the sequence.Each block pastes verbatim into /aod.discover --seed to create the matching GitHub Issue. No reformatting required.The whole guide is one docs/guides/CONSUMER_GUIDE_*.md file. Plain Markdown. Diffable. No tooling lock-in, no proprietary format.

View full example guides on GitHub (opens in new tab)

Run it

You need AOD-Kit cloned and make init already run. If you do not have either yet, work through Getting Started first — that page owns the install funnel.

/aod.kickstart

Running /aod.kickstart opens a short interview. It asks five questions about your idea, your target user, your key capabilities, and your GitHub org. Then it detects an active stack pack or asks you to pick one. Finally it writes a consumer guide and prints the file path. The whole flow runs in a single terminal session.

The guide lands at docs/guides/CONSUMER_GUIDE_{PROJECT_NAME}.md — a single Markdown file with setup phases, a feature summary table, and 6 to 10 seed-feature blocks in dependency order. Open it, scan the table, and start with the first feature.

Once the guide is written, feed each seed feature into /aod.discover --seed to create the matching GitHub Issues — one command per feature, in dependency order.

Next steps

Install AOD-KitStar on GitHub (opens in new tab)