SKILL.md
Doc
Write or update the documentation the caller needs, grounded in the current repository and its accepted intent. A small explanation needs no interview, coverage ledger or separate report. Select only the mode relevant to the task.
Modes
| Need | Scope and reference |
|---|---|
| Explain an API, command, code-map or architecture | Inspect its consumers and source; use code/API guidance or the codebase report when useful. |
| Create or improve a README | Lead with the user's problem and a working first-use path; preserve useful depth. See README craft. |
| Check an advertised install, upgrade or first-success path | Follow the selected package and current instructions in an authorized disposable environment. See developer journey. |
| Audit or scaffold OSS documentation | Compare existing docs with the requested pack. Create missing files; revise existing files only within the authorized request. See OSS pack. |
| Initialize missing entry documents | Create only explicitly requested missing files; report existing paths as skipped. See setup examples. |
| Bring docs current after a change, describe a change for reviewers, or write release notes for a range | Start from the exact diff and its public surface; fix what it proves wrong and ask about judgment calls. See change-driven docs. |
| Preserve a session for another context, or resume from one | Fill the handoff template and deliver it as described there; resume by checking it against current state. |
| Get facts or decisions only another person holds | Write one questionnaire they can answer alone; the caller sends it. |