Documentation

Patterns and structure for writing API reference documentation includingendpoint descriptions, request/response schemas, and error documentation.

Write comprehensive unit tests with high coverage using testing frameworks like Jest, pytest, JUnit, or RSpec. Use when writing tests for functions, classes, components, or establishing testing standards.

Fundamental reading and writing capability for the OCTAVE format. Inject this to give an agent basic structural competence without the overhead of full architectural specifications. Triggers on: octave format, write octave, octave syntax, structured output.

Design RESTful APIs following best practices for resource modeling, HTTP methods, status codes, versioning, and documentation. Use when creating new APIs, designing endpoints, or improving existing API architecture.

Review reception protocol - requires technical verification before implementingsuggestions. Prevents performative agreement and blind implementation.

TDD for process documentation - write test cases (pressure scenarios), watchbaseline fail, write skill, iterate until bulletproof against rationalization.

Patterns for writing clear, consistent API field descriptions includingtypes, constraints, examples, and edge cases.

Create comprehensive user guides, tutorials, how-to documentation, and step-by-step instructions with screenshots and examples. Use when writing user documentation, tutorials, or getting started guides.

Structured workflow for onboarding new services to the internal platformincluding infrastructure provisioning, observability setup, and documentation.

Modernize and improve legacy codebases while maintaining functionality. Use when you need to refactor old code, reduce technical debt, modernize deprecated patterns, or improve code maintainability without breaking existing behavior.

Create security policies, guidelines, compliance documentation, and security best practices. Use when documenting security policies, compliance requirements, or security guidelines.

Create comprehensive API reference documentation with OpenAPI/Swagger specs, REST endpoints, authentication, examples, and SDKs. Use when documenting REST APIs, GraphQL APIs, endpoint documentation, or OpenAPI specifications.

Carmack-level plan review via rp-cli context builder + chat. Use when reviewing implementation plans, architecture docs, or design specs. Triggers on mentions of plan review, design review, or architecture review.

Expert guidance for Dagster data orchestration including assets, resources, schedules, sensors, partitions, testing, and ETL patterns. Use when building or extending Dagster projects, writing assets, configuring automation, or integrating with dbt/dlt/Sling.

Gate 2: Feature relationship map - visualizes feature landscape, groupings,and interactions at business level before technical architecture.

Write effective user stories that capture requirements from the user's perspective. Create clear stories with detailed acceptance criteria to guide development and define done.

Gate 3: Technical architecture document - defines HOW/WHERE with technology-agnosticpatterns before concrete implementation choices.

Write comprehensive code documentation including JSDoc, Python docstrings, inline comments, function documentation, and API comments. Use when documenting code, writing docstrings, or creating inline documentation.

Development cycle feedback system - calculates assertiveness scores, analyzes promptquality for all agents executed, aggregates cycle metrics, performs root cause analysison failures, and generates improvement reports to docs/feedbacks/cycle-{date}/.

Analyze code complexity, cyclomatic complexity, maintainability index, and code churn using metrics tools. Use when assessing code quality, identifying refactoring candidates, or monitoring technical debt.