Agent skill
ext-outline-docs
Outline extension for documentation domain
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/ext-outline-docs
SKILL.md
Documentation Outline Extension
Extension for phase-2-outline in documentation domain.
Provides domain-specific knowledge for deliverable creation in documentation tasks. This is a knowledge document loaded as context - it does not replace the workflow.
Domain Detection
This domain is relevant when:
doc/ordocs/directory exists- Request mentions "AsciiDoc", "ADR", "interface specification", "documentation"
- Files have
.adocextension - Request mentions updating README or technical documentation
Domain Constraints
Component Rules
- AsciiDoc files MUST have blank line before lists
- Cross-references MUST use
xref:syntax - ADRs MUST follow numbered naming:
ADR-NNN-title.adoc - Interface specs MUST follow numbered naming:
IF-NNN-title.adoc - All documents should have proper heading hierarchy
Dependency Rules
- Documentation changes do NOT require unit tests
- Changes to
doc/directory do NOT trigger build verification - ADR changes require review of supersedes/superseded-by links
- Interface spec changes may require code traceability updates
Verification Rules
- AsciiDoc validation: Check for proper formatting and structure
- Link verification: Validate all internal cross-references
- Verification commands:
- ADRs: Check ADR numbering sequence and status consistency
- Interfaces: Check interface numbering and completeness
Deliverable Patterns
Grouping Strategy
| Scenario | Grouping |
|---|---|
| Single document update | One deliverable |
| ADR creation with related updates | One deliverable for all related ADRs |
| Interface spec with code traceability | One deliverable for spec, separate for code |
| Documentation sync with code | Doc deliverable depends on code deliverable |
Change Type Mappings
| Request Pattern | change_type | execution_mode |
|---|---|---|
| "add", "create", "new" ADR/doc | create | automated |
| "update", "fix" documentation | modify | automated |
| "supersede" ADR | modify | automated |
| "reorganize" docs | refactor | manual |
Standard File Structures
- ADRs:
doc/adr/ADR-NNN-{title}.adoc - Interfaces:
doc/interfaces/IF-NNN-{title}.adoc - Architecture:
doc/architecture/{topic}.adoc - General:
doc/{topic}/ - README:
README.mdorREADME.adoc
Impact Analysis Patterns
Detection Commands
| Change Type | Discovery Command |
|---|---|
| Broken xrefs | grep -r 'xref:' doc/*.adoc |
| ADR supersedes | grep -r 'Superseded by' doc/adr/ |
| Interface refs | grep -r 'IF-[0-9]' doc/ |
| README links | grep -r '\[.*\](.*\.adoc)' README.md |
Discovery Script
For comprehensive documentation analysis:
# Find all AsciiDoc files
find doc/ -name "*.adoc" -type f
# Check ADR sequence
ls -1 doc/adr/ADR-*.adoc 2>/dev/null | sort
# Check interface specs
ls -1 doc/interfaces/IF-*.adoc 2>/dev/null | sort
Batch Analysis Guidelines
- Process related documents together (e.g., ADR and its superseded docs)
- Check cross-references when modifying any document
- Validate heading hierarchy in modified documents
Related Skills
| Skill | Purpose |
|---|---|
pm-documents:cui-documentation |
General documentation standards |
pm-documents:adr-management |
ADR CRUD and formatting |
pm-documents:interface-management |
Interface spec CRUD and formatting |
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?