Skill Claude CodeCodex
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
9 1mo ago A 31 tokens
copy · 100% MIT
Skill Claude CodeCodex
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
9 1mo ago A 31 tokens
copy · 100% MIT
Skill Claude CodeCodex
Archive multiple completed changes at once. Use when archiving several parallel changes.
9 1mo ago A 23 tokens
copy · 88% MIT
Skill Claude CodeCodex
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.
9 1mo ago A 39 tokens
copy · 69% MIT
Skill Claude CodeCodex
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.
9 1mo ago A 39 tokens
copy · 100% MIT
Skill Claude CodeCodex
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.
9 1mo ago A 34 tokens
copy · 86% MIT
Skill Claude CodeCodex
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.
9 1mo ago A 40 tokens
copy · 73% MIT
Skill Claude CodeCodex
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
9 1mo ago A 26 tokens
copy · 80% MIT
Skill Claude CodeCodex
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.
9 1mo ago A 38 tokens
copy · 100% MIT
Skill Claude CodeCodex
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
9 1mo ago A 32 tokens
copy · 77% MIT
Instructions file
Instructions for fjpulidop/specrails-core, covering specrails-core, stack, repo layout, dev commands and environment.
9 1mo ago A 1,873 tokens
original MIT
doctor
12Command
Run the specrails health check to validate that all prerequisites are correctly configured for this repository.
9 1mo ago A 0 tokens
original MIT
specrails
13Plugin Claude Code
SpecRails Agent Workflow System — product-driven AI development pipeline. Installs 14 specialized agents and 20+ workflow skills: /specrails:implement, /specrails:setup, /specrails:get-backlog-specs, and more.
9 1mo ago A
tokens not measured
original MIT
architect
14Agent
Use this agent when the user invokes OpenSpec commands related to fast-forward (/opsx:ff) or continue (/opsx:continue). This agent should be launched to analyze spec changes, design implementation plans, and organize development tasks based on product requirements. Examples: Context: The user invokes the OpenSpec…
9 1mo ago A 177 tokens
original MIT
Agent
Specialized backend developer for the configured backend stack implementation. Use when tasks are backend-only or when splitting full-stack work across specialized developers in parallel pipelines.
9 1mo ago A 34 tokens
original MIT
Agent
Use this agent when backend files have been modified. Scan-and-report only. Scans for N+1 query patterns, connection pool safety issues, pagination safety problems, and missing database indexes. Do NOT use this agent to fix issues — it scans and reports only. Examples: Example 1: user: (orchestrator) Backend files…
9 1mo ago A 155 tokens
original MIT
developer
17Agent
Use this agent when an OpenSpec change is being applied (i.e., during the /opsx:apply phase of the OpenSpec workflow). This agent implements the actual code changes defined in OpenSpec change specifications, translating specs into production-quality code across the full stack. Examples: Example 1: user: "Apply the…
9 1mo ago A 128 tokens
original MIT
doc-sync
18Agent
Use this agent after tests are written to detect documentation drift and update docs — changelog entries, README updates, and API docs — keeping docs in sync with code changes. Runs as Phase 3d in the implement pipeline. Examples: Example 1: user: (orchestrator) Tests complete. Update docs for the implemented files.…
9 1mo ago A 136 tokens
original MIT
Agent
Specialized frontend developer for the configured frontend stack implementation. Use when tasks are frontend-only or when splitting full-stack work across specialized developers in parallel pipelines.
9 1mo ago A 34 tokens
copy · 86% MIT
Agent
Use this agent when frontend files have been modified. Scan-and-report only. Scans for bundle size regressions, accessibility violations (WCAG 2.1 AA), and render performance issues. Do NOT use this agent to fix issues — it scans and reports only. Examples: Example 1: user: (orchestrator) Frontend files were modified.…
9 1mo ago A 152 tokens
original MIT
Agent
Use this agent when the /specrails:implement pipeline produces conflict markers in Phase 4a (worktree merge), or when the user runs /specrails:merge-resolve directly. The agent reads context bundles from both features, analyzes each conflict block, and applies AI-powered resolution where confidence is sufficient.…
9 1mo ago A 165 tokens
original MIT
Agent
Use this agent to detect performance regressions after implementation. It benchmarks modified code paths, compares metrics against configured thresholds, and outputs a structured report. Runs as part of Phase 4 in the implement pipeline. Do NOT use this agent to fix regressions — it measures and reports only.…
9 1mo ago A 139 tokens
original MIT
Agent
Use this agent for read-only analysis tasks: backlog prioritization, VPC evaluation, codebase audits, spec gap analysis, dependency checks, and reporting. This agent reads specs, code, personas, and archived changes to produce structured reports. It never writes code or modifies files. Examples: Example 1: user…
9 1mo ago A 137 tokens
original MIT
Agent
Use this agent when the user invokes the opsx:explore command. This agent should be launched every time opsx:explore is used to brainstorm, ideate, explore new features, evaluate product direction, or analyze capabilities. Examples: Example 1: user: "/opsx:explore I want to think about how we could improve the user…
9 1mo ago A 181 tokens
original MIT