Menu
OpenAgentd workflow for keeping the compact feature catalogue and README aligned with user-visible changes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
OpenAgentd workflow for version bumps, release PRs, GitHub releases, and release notes.
Select and create accurate software architecture, workflow, interaction, data, state, and deployment diagrams.
Research first, propose a step-by-step implementation plan, and wait for explicit approval before writing any code.
Semantic search over the retained OpenAgentd feature catalogue, ADRs, and repository instructions using the turbovec experiment index.
OpenAgentd TDD workflow — write a failing test before the code that makes it pass, reproduce a bug with a test before fixing it. Use when implementing any logic, fixing any bug, or changing any existing behavior in backend (pytest) or frontend (Bun/RTL) code.
OpenAgentd testing reference — environment setup, run commands, and fix patterns for backend (pytest) and frontend (Bun/RTL). Load this for running, fixing, or adding coverage to existing tests. For writing a failing test before new code, use oad/test-driven-development instead.
| name | oad/docs |
| description | OpenAgentd workflow for keeping the compact feature catalogue and README aligned with user-visible changes. |
Sync the small set of product documentation affected by the current code changes. Called automatically by oad/commit — can also be used directly when the feature catalogue drifts.
Inspect git diff --cached or git diff HEAD, then choose the smallest durable record:
documents/docs/features.md; it is the canonical catalogue.README.md when users need to discover or act on it.adr-writing skill.documents/.make verify-docs after Markdown, README, feature-catalogue, or ADR changes.oad/commit.