| name | softcopy-manual |
| description | Build manual artifacts and maintain the semi-automatic manual manifest workflow. Use when formal manual or design documentation is needed after features are reviewed. Do not use to invent screenshots or UI that do not exist. |
softcopy-manual
Purpose
Produce manual drafts, manifest files, and trace records.
Triggers
- Approved
feature_map.yaml
- Need user manual, API manual, design spec, or hybrid manual
Non-triggers
- No feature boundaries
- No screenshot or command evidence
Required outputs
softcopy/outputs/manual/manual_manifest.stub.yamlsoftcopy/manual_manifest.yamlsoftcopy/outputs/manual/manual_outline.mdsoftcopy/outputs/manual/manual.mdsoftcopy/outputs/manual/manual_pages.jsonsoftcopy/outputs/manual/manual_report.mdsoftcopy/outputs/manual/manual_trace.json
Optional outputs
softcopy/outputs/manual/manual.pdfsoftcopy/outputs/manual/manual.docx
Hard rules
- Do not invent screenshots or pages
- Manifest must distinguish real UI, API diagrams, and command output
- Unapproved manifest cannot support ready-to-submit
Workflow summary
- Build a stub manifest.
- Let the operator fill screenshot paths and actual steps.
- Normalize to the formal manifest.
- Render the manual and trace file.
