fjpulidop
UserChain-of-agents system to develop software.
Categories
Indexed Skills (42)
auto-propose-backlog-specs
sr:auto-propose-backlog-specs — Generate new feature ideas through product discovery, create GitHub Issues.
compat-check
sr:compat-check — Snapshot the API surface and detect breaking changes against a prior baseline. Generates a migration guide when breaking changes are found.
doctor
Run diagnostics on the sr plugin installation. Checks that all agents are available, required tools are installed, config files are valid, and memory directories exist. Outputs a health report with actionable fixes.
get-backlog-specs
sr:get-backlog-specs — View product-driven backlog from GitHub Issues and propose top 3 for implementation.
health-check
Run a comprehensive codebase health check — tests, linting, coverage, complexity, and dependency audit. Compare with previous runs to detect regressions.
memory-inspect
Inspect and manage agent memory directories. Lists all sr-* agent memory stores, shows per-agent stats (file count, size, last modified), displays recent entries, and detects stale or orphaned files.
opsx-apply
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
opsx-archive
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
opsx-bulk-archive
Archive multiple completed changes at once. Use when archiving several parallel changes.
opsx-continue
Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.
opsx-diff
Show a before/after diff of OpenSpec spec changes for a given change. Highlights additions, removals, and behavioral modifications across acceptance criteria, flows, and constraints. Supports markdown and JSON output.
opsx-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
opsx-ff
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
opsx-new
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
opsx-onboard
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
opsx-sync
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
opsx-verify
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
propose-spec
Explore a spec idea and produce a structured proposal
refactor-recommender
sr:refactor-recommender — Scan the codebase for refactoring opportunities ranked by impact/effort ratio. Optionally creates GitHub Issues for tracking.
setup
Initialize a project with the SpecRails workflow. Generates project-specific data files: .specrails/config.yaml, personas, memory directories, backlog config, and CLAUDE.md snippet. Does NOT copy logic files — the sr plugin already provides all agents, skills, and commands.
telemetry
Inspect per-agent execution metrics: token usage (input/output/cache), estimated API cost, run count, average duration, and success/failure rate. Reads Claude CLI JSONL session logs and agent-memory files. Outputs a cost dashboard with trend indicators and optimization recommendations.
vpc-drift
Detect when user personas defined in the VPC are drifting from actual usage patterns. Compares persona Jobs/Pains/Gains against the product backlog, implemented features, and agent memory to surface alignment gaps and recommend VPC updates.
why
sr:why — Search explanation records written by specrails agents during the OpenSpec implementation pipeline.
batch-implement
Run the implement pipeline over multiple backlog tickets in one session. Per ticket: spawn architect → spawn developer → spawn reviewer (the same three-phase pipeline $implement runs), then move to the next. Sequential by default; parallel only when the user explicitly opts in AND the tickets are independent. Reports an aggregated verdict at the end. Use when the user invokes `$batch-implement #N #M #K` or `$batch-implement --status todo`.
implement
Implement a single backlog ticket through a multi-phase pipeline: architect plans (OpenSpec proposal+design+tasks+specs), one or more developers code in TDD order, one or more reviewers validate in parallel. Routing is dynamic — the orchestrator inspects which rail skills are installed in .codex/skills/rails/ and spawns the specialists that apply to the change's scope. Reads .specrails/local-tickets.json, closes the ticket in place, reports concisely. Use when the user invokes `$implement #N` or `$implement <free-form>`.
merge-resolve
User-facing entry point for resolving git merge conflicts. Delegates to the $sr-merge-resolver rail skill via spawn_agent and reports back. Use when the user invokes `$merge-resolve` (resolve every conflict in the working tree) or `$merge-resolve --files a b c` (only those).
retry
Resume a previously-attempted $implement pipeline for a ticket. Detects what's already on disk (OpenSpec change package, partial code, ticked tasks.md) and re-invokes $implement so the architect/developer/reviewer agents skip work that's already correct and pick up where the prior run left off. Use when the user invokes `$retry #N` after a $implement run that ended in `todo` or `blocked`.
sr-architect
Architect role for the specrails implement pipeline. Reads a backlog ticket, surveys the repo, produces (a) an OpenSpec change package under openspec/changes/<slug>/ and (b) a plan artefact under .specrails/agent-memory/explanations/. Does NOT write production code. Invoked by the implement orchestrator via $sr-architect after a spawn_agent / send_message handoff.
sr-developer
Developer role for the specrails implement pipeline. Reads the architect's design + tasks.md and implements them in TDD order: for each task, write a failing test first, run it to confirm it fails, then write the minimum production code to make it pass, then re-run. Reports the files changed. Does NOT review its own work beyond the per-task test cycle. Invoked by the implement orchestrator via $sr-developer.
enrich
Full-tier install ritual for an existing specrails project. Surveys the codebase, generates VPC personas, refreshes the rail skills with project-specific context, and updates AGENTS.md's managed block. Single-agent flow — does NOT spawn the implement pipeline. Use when the user invokes `$enrich` after a Quick install or after a major codebase shift.
sr-backend-developer
Backend-specialist developer for the specrails implement pipeline. Use when the architect's plan touches API routes, server middleware, DB migrations, background jobs, or message queues. Walks tasks.md in TDD order like sr-developer but biased toward integration tests against real (or test-container) services. Invoked via $sr-backend-developer.
sr-backend-reviewer
Backend-specialist reviewer for the specrails implement pipeline. Validates API contracts, validation completeness, authorization coverage, error shape stability, idempotence, and migration safety on top of the standard sr-reviewer checks. Findings-only. Invoked via $sr-backend-reviewer.
sr-doc-sync
Documentation-sync specialist for the specrails workflow. Reads recent commits and the docs surface (README.md, docs/, AGENTS.md managed block, openspec/specs/), identifies drift between docs and code, and writes the targeted updates. Does NOT modify production code. Invoked via $sr-doc-sync.
sr-frontend-developer
Frontend-specialist developer for the specrails implement pipeline. Use when the architect's plan touches React/Vue/Svelte/HTML/CSS surfaces and the change benefits from UI-specific judgement (accessibility, responsive layout, framework idioms, design tokens). Walks tasks.md in TDD order like sr-developer but biased toward component-level tests (React Testing Library / Vue Test Utils / Playwright component) and visual invariants. Invoked via $sr-frontend-developer.
sr-frontend-reviewer
Frontend-specialist reviewer for the specrails implement pipeline. Use when the developer changed UI surfaces. Validates UI behaviour, accessibility, keyboard reachability, responsive layout, and design-token usage on top of the standard sr-reviewer checks. Findings-only — never modifies code. Invoked via $sr-frontend-reviewer.
sr-merge-resolver
Merge-conflict resolver for the specrails implement pipeline. Called when the orchestrator's worktree merge produces conflict markers, or when the user invokes $merge-resolve directly. Reads the conflict, analyses the intent of each side, applies a resolution where confidence is high, or leaves clean marker text where it isn't. Invoked via $sr-merge-resolver.
sr-performance-reviewer
Performance-focused reviewer for the specrails implement pipeline. Checks for N+1 queries, hot-loop allocations, unbounded inputs, unnecessary re-renders, and missing indexes on top of the standard sr-reviewer contract. Findings-only. Invoked via $sr-performance-reviewer.
sr-product-analyst
Product analyst for the specrails workflow. Reads the current state of the backlog (.specrails/local-tickets.json) and the codebase, then reports on coverage, drift, and recommended next moves. Does NOT propose new tickets (that's sr-product-manager) and does NOT implement. Invoked via $sr-product-analyst.
sr-product-manager
Product role for the specrails workflow. Reads the project's existing artefacts (README, openspec/specs/, .specrails/local-tickets.json, code surface) and proposes a coherent backlog of new tickets — each one a single, testable change with acceptance criteria. Does NOT implement. Invoked via $sr-product-manager, typically by $auto-propose-backlog-specs.
sr-reviewer
Reviewer role for the specrails implement pipeline. Validates the entire implementation: the OpenSpec change package (proposal/design/tasks/specs) is well-formed, the developer's code matches the design's public API and invariants, every tasks.md box is ticked, the tests cover every spec scenario, and the project's full test/build suite passes. Writes a confidence-score.json artefact. Does NOT modify the developer's code. Invoked via $sr-reviewer.
sr-security-reviewer
Security-focused reviewer for the specrails implement pipeline. Checks for injection, broken auth, sensitive data exposure, broken access control, and dependency vulnerabilities on top of the standard sr-reviewer contract. Findings-only. Invoked via $sr-security-reviewer.
sr-test-writer
Test-writing specialist for the specrails workflow. Reads a target file or directory, identifies untested observable behaviours, writes a balanced test suite, runs it, and reports coverage delta. Does NOT modify production code. Invoked via $sr-test-writer.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.