project-document-discovery — SKILL.md

Variant: standard · When to use: invoked to turn a project idea into a proportional, capability-scoped plan of the documents the project needs; returns a three-key JSON (capability_map + product_capabilities + manifest); control passes back to the caller.

Overview

Given a software/product project idea, this skill decides which documents the project needs to ship to production, and what it takes to produce each — the producer role, the tools/providers, the skills, and which other documents it depends on. It is discovery only: it picks the set and describes how each will be produced, never how to author a document (that is a separate per-document authoring skill). The guiding discipline is proportionality — the document set is sized to the project.

The skill runs as two explicit internal phases within a single model invocation:

• Phase A — Classify + Identify: classify the project across 10 dimension clusters → identify the product's distinct capability areas (4-signal algorithm + sizing tests) → produce capability_map JSON and product_capabilities list.
• Phase B — Fan-out Manifest: drive shared-document selection from classification flags → generate per-capability document entries from the capability list (fan-out rules) → attach DAG edges → self-check.

Output: three-key JSON {capability_map, product_capabilities, manifest}.

When to activate