Organize new features, complex implementations, and architecture changes into the SPARC stages: specification, pseudocode, architecture, refinement, and completion. Define requirements and acceptance criteria, consult existing patterns, and record lessons for future work.
- Defining requirements for a new feature
- Organizing a complex implementation
- Planning an architecture change
ruvnet/ruflo☆ 77.1KUpdated Oct 19, 2026
Turn an approved specification into pseudocode, a plain outline of program logic, and an architecture defining module responsibilities and API inputs and outputs. After user confirmation, proceed with implementation and unit tests based on those designs.
- Turning an approved specification into pseudocode
- Defining module boundaries and dependency rules
- Designing API inputs, outputs, and error responses
ruvnet/ruflo☆ 77.1KUpdated Oct 19, 2026
Turn a feature idea into a structured specification before coding. Review requirements, system connections, constraints, and failure scenarios, define testable acceptance criteria, and save the specification in memory for later development phases.
- Defining requirements before building a new feature
- Writing testable acceptance criteria
- Documenting constraints and failure scenarios
ruvnet/ruflo☆ 77.1KUpdated Oct 19, 2026
Turn specifications and designs into working code using test-driven development: write failing tests, implement enough code to pass, then refactor. The workflow also covers error handling, performance improvements, documentation, and coordinated changes across components.
- Implementing a feature from specifications and designs
- Developing authentication or APIs with tests
- Refactoring code while checking test results
ruvnet/ruflo☆ 77.1KUpdated Oct 19, 2026
Review implemented features against their requirements, add missing tests, and check performance constraints. Produce documentation, a table linking requirements to code and tests, and evidence showing whether the feature is ready for deployment.
- Review an implementation against its specification
- Add tests for uncovered requirements
- Link requirements to code and passing tests
ruvnet/ruflo☆ 77.1KUpdated Oct 19, 2026
Organize software development from requirements and architecture through testing, review, and deployment. Use specialized agent roles, shared memory, and test-driven development, where tests are written before code, to coordinate work across the project.
- Plan and implement a new feature
- Refactor legacy code with supporting tests
- Review code security and performance
ruvnet/RuView☆ 98.8KUpdated Oct 19, 2026
Turn software development goals into manageable milestones with clear deliverables, dependencies, effort estimates, and success criteria. Use it to plan feature implementation, bug fixes, refactoring, performance improvements, and testing work.
- Planning OAuth2 authentication implementation
- Setting measurable database performance targets
- Breaking refactoring into incremental steps
ruvnet/ruflo☆ 77.1KUpdated Oct 19, 2026
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
The English summary is being prepared. Showing the original description.
ruvnet/RuVector☆ 4.6KUpdated Oct 19, 2026
Use when turning images or photos into 3D meshes with Sparc3D models on Scenario via MCP: single-image or multi-view image-to-3D, watertight meshes for game assets, AR/VR, or 3D printing, mesh-only versus PBR-textured output, face count targets, resolution tiers, or reconstructing human heads and busts with the Portrait variants. Keywords: Sparc3D 2.1 and 2.0, Hitem3D, image to 3D, img23d, multiview, watertight, PBR, GLB, OBJ, STL, FBX.
The English summary is being prepared. Showing the original description.
scenario-labs/skills☆ 1.1KUpdated Oct 19, 2026
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
The English summary is being prepared. Showing the original description.
ruvnet/agentic-flow☆ 822Updated Oct 12, 2026
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
The English summary is being prepared. Showing the original description.
ruvnet/ruv-FANN☆ 387Updated Aug 9, 2026
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
The English summary is being prepared. Showing the original description.
spencermarx/open-code-review☆ 379Updated Jul 28, 2026
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
The English summary is being prepared. Showing the original description.
ruvnet/midstream☆ 149Updated Oct 10, 2026
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
The English summary is being prepared. Showing the original description.
ruvnet/marketing☆ 129Updated May 23, 2026
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
The English summary is being prepared. Showing the original description.
ruvnet/agentdb☆ 93Updated Oct 12, 2026
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
The English summary is being prepared. Showing the original description.
oimiragieo/agent-studio☆ 42Updated Jul 14, 2026
Agent skill for implementer-sparc-coder - invoke with $agent-implementer-sparc-coder
The English summary is being prepared. Showing the original description.
majiayu000/claude-skill-registry-data☆ 27Updated Oct 18, 2026
Improve existing code through repeated cycles of testing, implementation, and refactoring. The skill covers performance bottlenecks, error recovery, code coverage, and documentation, helping developers refine behavior and structure while keeping tests passing.
- Refactoring existing code while keeping tests passing
- Adding tests before implementing expected behavior
- Investigating slow database access and cache usage
ruvnet/ruflo☆ 77.1KUpdated Oct 12, 2026
Turn specifications into pseudocode, a language-independent outline of program logic. Define data structures, handle edge cases, analyze time and memory requirements, and document design patterns and optimization opportunities before implementation.
- Turning specifications into clear processing steps
- Comparing data structures and computational costs
- Planning error handling and edge cases before coding
ruvnet/ruflo☆ 77.1KUpdated Oct 19, 2026
Turn specifications and algorithm outlines into a system architecture. Define components, interfaces, data structures, and deployment plans, then document technology choices, security measures, failure handling, and plans for supporting increased usage.
- Turn specifications into a system design
- Define component responsibilities and API interfaces
- Plan for increased traffic and component failures
ruvnet/ruflo☆ 77.1KUpdated Oct 19, 2026
Organize software development from requirements and design through testing, review, and deployment. Uses Claude Flow to coordinate specialized agents, share decisions across sessions, and guide implementation with tests written before code.
- Developing a feature from requirements through review
- Refactoring legacy code with supporting tests
- Investigating bugs and adding regression tests
ruvnet/ruflo☆ 77.1KUpdated Oct 19, 2026
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
The English summary is being prepared. Showing the original description.
ibragimov-oasis/vibe-coder☆ 3Updated Jun 24, 2026
Think and work like an expert Microbial Ecologist. Use when a task calls for Microbial Ecologist judgment. Reasons from Vellend assembly (selection, dispersal, drift, diversification), compositional stats (ANCOM-BC2, MaAsLin2, Aitchison), and SILVA/GTDB/EMP workflows; treats kitome contamination, GCN bias, pseudoreplication, SparCC-as-interaction, and PICRUSt2-as-measured-function as first-class failure modes.
The English summary is being prepared. Showing the original description.
K-Dense-AI/scientific-agents☆ 218Updated Oct 3, 2026