C-Spec Discover

Discovers and inventories all vertical slices for an MVP, outputting a structured manifest to .cspec/manifest.md.

Input Mode Detection

Determine mode from context:

• User provides a document (file path or pasted content) → document-driven or hybrid mode
• No document provided → interactive interview mode

Re-run Behavior

If .cspec/manifest.md already exists, present the existing slices and ask the user:

• Amend — Add, remove, or modify slices in the existing manifest. Preserve statuses of existing slices.
• Start fresh — Discard existing manifest and begin discovery from scratch. Warn that this does not delete already-written slice spec files.

Interactive Process

1. Understand the product — Ask what it is, who it's for, what problem it solves. One question at a time. Prefer multiple choice when possible.
2. Identify features — Ask about the major user-facing capabilities.
3. Break into vertical slices — Each slice is one user flow at user-story granularity (e.g., "user signs up with email" not "authentication system"). One flow per slice.
4. Group into domains — Cluster related slices under domain names (e.g., auth, billing, content).
5. Determine ordering — Identify dependencies between slices and assign priority. Slices with no dependencies come first.
6. Present for validation — Show the complete slice inventory to the user for review before writing the manifest.

Document-Driven Process

1. Read the document — Analyze the provided brief, PRD, or product description.
2. Extract slices and domains — Identify vertical slices and group them.
3. Present findings — Show extracted slices to the user for validation.
4. Fill gaps (hybrid) — Ask follow-up questions one at a time for anything unclear or missing from the document.
5. Finalize — Confirm the complete inventory with the user before writing.

Manifest Output

Write the manifest to .cspec/manifest.md using this template:

# [Product Name] — Manifest

## Product Summary

[Brief description of the product, target users, and core value proposition]

## Tech Preferences

[Any tech stack preferences or constraints expressed during discovery, or "None specified"]

## Domains

### [Domain Name]

[Brief description of this domain's scope]

### [Domain Name]

[Brief description of this domain's scope]

## Slice Inventory

| Slice | Domain | Description | Priority | Dependencies | Status |
|-------|--------|-------------|----------|--------------|--------|
| [slice-name] | [domain] | [One-line description] | [1-N] | [comma-separated slice names, or "none"] | unwritten |

All slices start with status unwritten. Priority 1 is highest (build first).

Completion

After writing the manifest, inform the user:

"Manifest written to .cspec/manifest.md with [N] slices across [N] domains. Run /cspec-write to begin writing slice specs."