project-docs

Plugin project-docs from marketplace mrstroz-marketplace in mrstroz/claude-code-plugins. Commands read from the repo's manifest — 14 days ago.

Skills (5)

• docs-init

  Set up the spec/ADR/plan documentation system in a project — creates docs/spec/ (what the system does, in numbered sections), docs/adr/ (why each decision was made, one file per decision, with a template and a register), docs/plan/ (milestones and PREFIX-NN tasks that link to spec sections instead o

• docs-style

  Writing rules for spec, ADR and plan documents — short, checkable, scannable, plain language, with hard length budgets and every claim about system behaviour pointing at code someone actually opened. Read this before writing the first paragraph, not after; fixing a finished draft costs more than dra

• docs-summary

  Read docs/plan/ back as one short table — every task as a row with its id, priority marker and a plain-language line saying what has to happen, ordered by priority rather than by file. Answers "what is left" without anybody opening the milestone files and counting checkboxes by eye. Asks for the sco

• docs-sync

  Mirror the tasks in docs/plan/ to GitHub Issues and read the answers back — creates an issue for every open task, keeps titles and labels matching the plan, ticks a checkbox when its issue is closed, and closes an issue when its task is finished or rejected. Works only where docs/docs.config.json tu

• docs-task

  Run a task from docs/plan/ end to end, and close the documentation loop so docs/spec, docs/adr and docs/plan keep describing what the code actually does. Two entry points. Starting work — "zrób APP-12", "weź następne zadanie", "co teraz", "kontynuuj plan", "zacznij M2", "do HUE-21", "next task", "wh