rpamis
Official@rpamis · China
More Efficient, Easier to Use, and Less Annoying
Agent Skills by rpamis
Showing 47 vetted skills indexed across 1 GitHub repositories.
using-git-worktrees
Creates isolated git worktree workspaces with native tool detection and baseline test verification.
test-driven-development
Enforces red-green-refactor test-driven development workflow for features and bugfixes.
systematic-debugging
Diagnose bugs through a four-phase root cause investigation process before proposing fixes.
dispatching-parallel-agents
Dispatch parallel subagents to investigate independent failures across separate problem domains concurrently.
executing-plans
Executes written implementation plans task-by-task with verification checkpoints and review gates.
finishing-a-development-branch
Guides completion of development branches through structured merge, pull request, or cleanup options.
brainstorming
Guides collaborative design exploration and spec writing before any implementation work begins.
writing-plans
Generates detailed multi-task implementation plans from specs with TDD steps and exact file paths.
requesting-code-review
Dispatches a code reviewer subagent to evaluate git diffs against requirements before merging.
receiving-code-review
Guides verification and implementation of code review feedback with technical rigor.
writing-skills
Create and test agent skills using test-driven development methodology.
verification-before-completion
Enforces running verification commands before claiming work is complete or passing.
subagent-driven-development
Executes implementation plans by dispatching fresh implementer and reviewer subagents per task.
openspec-apply-change
Implements tasks from an OpenSpec change using the openspec CLI.
openspec-explore
Explores ideas, investigates codebases, and clarifies requirements through conversational analysis with ASCII diagrams.
openspec-verify-change
Verify implementation matches change specs, tasks, and design artifacts before archiving.
openspec-new-change
Scaffolds a new OpenSpec change directory using the artifact-driven workflow.
openspec-archive-change
Archives completed OpenSpec changes with artifact, task, and spec sync verification.
openspec-onboard
Guides users through a complete OpenSpec change workflow cycle with narrated phases.
openspec-propose
Generates complete OpenSpec change proposals with design, specs, and task artifacts.
openspec-bulk-archive-change
Archives multiple completed openspec changes in one batch operation with conflict resolution.
openspec-continue-change
Creates the next artifact in an OpenSpec change workflow using the openspec CLI.
openspec-sync-specs
Sync delta specs from an OpenSpec change into main specification files.
openspec-ff-change
Generates all OpenSpec change artifacts in one pass until implementation-ready.
Frequently Asked Questions About rpamis
FAQPage SchemaWhat specific tasks does rpamis enable for engineering teams?▼
The platform enables structured development through a five-phase cycle including design, build, verification, and archival. It facilitates the creation of skeleton changes, generates executable build plans from OpenSpec designs, and manages the merging of delta specifications into main project branches.
Which technical personas benefit from using these capabilities?▼
Software engineers, release managers, and technical architects benefit from these capabilities. The system is designed for teams requiring rigorous adherence to OpenSpec semantics during the development lifecycle, particularly those managing complex change requests and delta specification updates.
What are the core prerequisites for implementing this development cycle?▼
Implementation requires the adoption of OpenSpec design standards and the establishment of a five-phase development pipeline. Teams must define their project structure using OpenSpec semantics to enable the generation of build plans and the subsequent verification and archival of development changes.