<< All versions

Skill v1.0.0

currentAutomated scan100/100
antostr/team-workflow/write-docs
──Details
PublishedNovember 17, 2026 at 12:24 AM
Content Hashsha256:0f55cd0278b276d1...
Git SHAad9fc2683db4
──Files
Files (1 file, 1.3 KB)
SKILL.md1.3 KBactive
SKILL.md · 24 lines · 1.3 KB

name: write-docs description: Write or refresh documentation for people from the project memory - architecture, onboarding, changelog, README - with every fact checked against the code argument-hint: "[architecture | onboarding | changelog | readme | all]" disable-model-invocation: true metadata: version: "1.0.0"


Use the team skill to write documentation from the project memory: $ARGUMENTS

  1. Read docs/memory (INDEX, STATE, MAP, the area cards, DECISIONS, PLAYBOOKS, ACCESS). If it

is missing, offer /team:setup-memory first; if it looks outdated, have doc-keeper fix it before writing anything from it.

  1. Agree what to write, where and in which language (AskUserQuestion; ask_question in agy):

architecture overview (for example docs/ARCHITECTURE.md), onboarding or contributing guide, changelog from STATE.md and git log, README sections. Existing files are updated, not replaced.

  1. Run the assignment wizard for technical-writer.
  2. Every fact comes from the memory and is checked against the code; every command shown is run

first. Nothing in the documentation may contradict the memory: if they disagree, the code decides and the memory is corrected too.

  1. Report the files written, what each covers, and the facts that could not be verified.
All versions