write-documentslisted

# Document Writing Guide This skill contains document templates and formatting rules. ## Verb Mapping This skill implements: - [WRITE-INFO] - Create INFO documents (use INFO_TEMPLATE.md) - [WRITE-SPEC] - Create SPEC documents (use SPEC_TEMPLATE.md) - [WRITE-IMPL-PLAN] - Create IMPL documents (use IMPL_TEMPLATE.md) - [WRITE-TEST-PLAN] - Create TEST documents (use TEST_TEMPLATE.md) - [WRITE-FIX] - Create FIX documents (use FIXES_TEMPLATE.md) - [WRITE-FAIL] - Create/update FAILS.md (use FAILS_TEMPLATE.md) - [WRITE-REVIEW] - Create _REVIEW.md documents (use REVIEW_TEMPLATE.md) - [WRITE-TASKS-PLAN] - Create TASKS documents (use TASKS_TEMPLATE.md) - [WRITE-STRUT] - Create/insert STRUT plans (use STRUT_TEMPLATE.md) ## MUST-NOT-FORGET - Use lists, not Markdown tables - No emojis - ASCII only, no `---` markers between sections - Header block: Doc ID (required), Goal (required), Target file, Depends on (omit if N/A) - Every document MUST have a unique ID - Reference other docs by filename AND Doc ID: `_SPEC_CRAWLER.md [CRWL-SP01]` - Be exhaustive: list ALL domain objects, actions, functions - Document History section at end, reverse chronological - Use box-drawing characters (├── └── │) for trees - SPEC, IMPL, TEST documents MUST have MUST-NOT-FORGET section (after header block, before TOC) ## Document Writing Rules - Enumerations: use comma-separated format (`.pdf, .docx, .ppt`), NOT slash-separated (`.pdf/.docx/.ppt`) - Ambiguous modifiers: when a clause can attach to multiple