From rpa-feat
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rpa-feat:rpa-featThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
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.
npx claudepluginhub evilfreelancer/rpa-skills --plugin rpa-featCreates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.