project-document-discovery — SKILL.md

Variant: standard · When to use: invoked to turn a project idea into a proportional plan of the documents the project needs, each tagged with what it takes to produce it; returns the plan; 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, composed with a template skill). The guiding discipline is proportionality — the document set is sized to the project, never a fixed taxonomy applied regardless of scale.

When to activate

• ✅ Deciding which documents a new project needs before any document is produced.
• ✅ Producing a "document plan" / manifest that a later stage reads to produce the documents (and later to plan the build).
• ✅ Sizing a documentation set proportionally (a lean MVP vs a full product).

Do NOT activate when:

• Authoring or templating a specific document (writing the PRD, drafting the architecture doc) — use a per-document authoring skill + a content/template skill.
• Discovering the build-time engineering roster (what roles/tools/providers it takes to build the product) — that is a separate, later analysis done from the finished documents.
• The project already has an agreed document set.