Synthesizes all pipeline handoffs into a single human-readable project brief. Use when user says "generate docs", "create documentation", "document the project", or after validation passes. Do NOT use for deployment (use fabric-deploy) or architecture design (use fabric-design).
68
83%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
⚠️ Artifacts-only mode: When
deploy_modeisartifacts_only, this skill is NOT invoked — the pipeline runner handles this phase deterministically. The instructions below apply only whendeploy_modeislive.
Goal: Produce ONE deliverable —
docs/project-brief.md— that a CTO can read in 10 minutes.
⚡ Pre-generated brief: The runner writes a structured
project-brief.mdsynthesized from all handoffs before this skill is invoked, with<!-- AGENT: FILL -->markers where narrative polish is needed. Your job: (1) verify facts against the source handoffs, (2) add narrative polish so the brief reads like a CTO memo rather than a template, (3) replace every<!-- AGENT: FILL -->marker.
Read these files in parallel from _projects/[name]/docs/ (all are independent inputs):
discovery-brief.md — problem statement and signalsarchitecture-handoff.md — items, waves, decisions, trade-offs, diagramdeployment-handoff.md — what was deployed, config rationale, manual stepstest-plan.md — acceptance criteria, edge casesvalidation-report.md — pass/fail resultsproject-brief.mdEdit _projects/[name]/docs/project-brief.md in place (it is pre-generated).
Follow the template in references/documentation-templates.md. Key rules:
The brief must answer these 5 questions:
project-brief.mdb986f41
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.