Sparc Spec
Skill Verified ActiveRun the SPARC Specification phase — gather requirements, define acceptance criteria, identify constraints, and store the spec in memory
To provide a structured and automated way to gather, define, and store software requirements before development begins, ensuring a clear foundation for subsequent project phases.
Features
- Automated requirements gathering
- Definition of acceptance criteria
- Identification of project constraints
- Mapping of edge cases and failure modes
- Storage of specifications in memory
Use Cases
- Starting a new feature or project with clear requirements
- Ensuring all necessary criteria and constraints are defined before coding
- Creating a foundational specification for subsequent development phases
- Standardizing requirements gathering across a team or organization
Non-Goals
- Writing code
- Designing the architecture
- Generating pseudocode
- Completing the entire software development lifecycle
Scope
- info:Tool surface sizeThe specific skill `sparc-spec` exposes a small number of tools, but the overall Ruflo project has a very large tool surface area across its plugins.
Installation
First, add the marketplace
/plugin marketplace add ruvnet/ruflo/plugin install ruflo-sparc@rufloQuality Score
VerifiedTrust Signals
Similar Extensions
Using Superpowers
99Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Caveman
99Decision guide for delegating to caveman-style subagents. Tells the main thread WHEN to spawn `cavecrew-investigator` (locate code), `cavecrew-builder` (1-2 file edit), or `cavecrew-reviewer` (diff review) instead of doing the work inline or using vanilla `Explore`. Subagent output is caveman-compressed so the tool-result injected back into main context is ~60% smaller — main context lasts longer across long sessions. Trigger: "delegate to subagent", "use cavecrew", "spawn investigator/builder/reviewer", "save context", "compressed agent output".
Omc Plan
99Strategic planning with optional interview workflow
Deep Interview
99Socratic deep interview with mathematical ambiguity gating before explicit execution approval
Kaizen
99Use when Code implementation and refactoring, architecturing or designing systems, process and workflow improvements, error handling and validation. Provide tehniquest to avoid over-engineering and apply iterative improvements.
Ce Plan
99Create structured plans for multi-step tasks -- software features, research workflows, events, study plans, or any goal that benefits from breakdown. Also deepens existing plans with interactive sub-agent review. Use when the user says 'plan this', 'create a plan', 'how should we build', 'break this down', or when a brainstorm doc is ready for planning. Use 'deepen the plan' or 'deepening pass' for the deepening flow. For exploratory requests, prefer ce-brainstorm first.