// Run when the user invokes /rpa-feat together with a clear feature description (for example issue text). BDD workflow: plan, failing tests, implementation, green tests, full suite, docs and examples, linter at the end. Will not work correctly without the user supplying what to build.
Run when the user invokes /rpa-bugfix together with a clear bug description (expected vs actual, reproduction). Reproduction test first, then fix, full test suite, short report. Will not work correctly without the bug details.
Run when the user invokes /rpa-gen-rules or asks to create or refresh agent project rules (Cursor .mdc, Claude Code CLAUDE.md and .claude/rules). Infers from specs, docs, and code. Rules use a layered-cake model (implement inner layers with no dependencies first, then the next layer) and BDD-style delivery. No separate user brief required.
Run when the user invokes /rpa-init or asks to onboard or warm up context on a repository. The agent studies code, reads documentation and test code, sets up the dev environment as the project expects, runs tests, and writes a short project report. No extra user brief is required.
Use when the user needs logical analysis, reasoning chains, or critical thinking grounded in classical formal logic (concepts, judgments, syllogisms, induction, fallacies). Triggers: analyzing arguments, checking validity of inferences, classifying concepts or judgments, building syllogisms, identifying logical errors, solving logic textbook problems, constructing proofs, or evaluating hypotheses and analogies.
| name | rpa-feat |
| version | 1.0.0 |
| description | Run when the user invokes /rpa-feat together with a clear feature description (for example issue text). BDD workflow: plan, failing tests, implementation, green tests, full suite, docs and examples, linter at the end. Will not work correctly without the user supplying what to build. |
The user must include /rpa-feat and a concrete feature description in the same message or immediately after (scope, acceptance criteria, edge cases, issue text). If there is no actionable description, ask once for the minimum needed or stop.
Behavior is anchored in tests. The loop is plan, red, green, full regression, documentation, then quality tools.
.venv and project conventions. Respect .cursor/rules/ or .claude/rules/ if present.pre-commit run -a). Fix what it reports.Short summary: what shipped, tests added or changed, full suite result, docs touched, linter result.