project-docs

Plugin project-docs in ttorres33/project-docs. Commands read from the repo's manifest — 1 month ago.

Skills (5)

• ab-test

  Documents A/B tests with variants, hypothesis, measurement plan, and conclusions. Use when the user mentions running an A/B test, comparing two variants, or wanting to measure/test something systematically.

• architecture

  Keeps project ARCHITECTURE.md up-to-date with system design, patterns, and conventions. Use when infrastructure changes, new patterns are established, data models change, or when user explicitly requests /architecture command.

• convert-flat-process-notes-to-dir

  Converts a legacy flat process-notes.md file into the per-entry process-notes/ folder format. Use when the process-notes skill refuses to write because it detects the old format, or when the user explicitly requests /project-docs:convert-flat-process-notes-to-dir.

• process-notes

  Maintains comprehensive project history in a process-notes/ folder that documents work process, decisions, dead ends, and progress. Each entry is a separate file named by timestamp + slug. Use when context window fills up (approaching 60% of token budget), when making key decisions or reaching miles

• readme

  Keeps project README.md up-to-date with current state of the project. Use when structural changes occur, behavior changes, setup/config changes, feature additions/removals, or when user explicitly requests /readme command.

Slash commands (7)

• /project-docs:ab-test

  Document an A/B test with variants, hypothesis, and measurement plan

• /project-docs:about

  Show plugin documentation and usage

• /project-docs:all-docs

  Update all project documentation (README, ARCHITECTURE, process-notes)

• /project-docs:architecture

  Update ARCHITECTURE.md to document system design and patterns

• /project-docs:code-review

  Review uncommitted code changes for consistency, quality, and maintainability

• /project-docs:plan-review

  Review the current plan for consistency, duplicates, and complexity

• /project-docs:readme

  Update README.md to reflect current project state

Subagents (2)

• code-reviewer

  Reviews uncommitted code changes for consistency with project architecture, code quality, and maintainability. Use after writing code and before committing.

• plan-reviewer

  Reviews implementation plans for consistency with project architecture, duplicate code, and unnecessary complexity. Use after creating a plan and before implementation.

Similar plugins