Skip to content
Back to skills

Sparc Methodology

ASecurity

SPARC development workflow (Specification, Pseudocode, Architecture, Refinement, Completion). Use when: new features, complex implementations, architectural changes. Skip when: simple fixes, documentation, configuration.

  • 2 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 11, 2026
toolsbashdocumentation

Works with

  • cli

Security analysis

A100/100

Scanned September 11, 2026

npx -y skills add ibragimov-oasis/vibe-coder --skill sparc-methodology --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Sparc Methodology?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Sparc Methodology
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ibragimov-oasis-sparc-methodology-d4cc4c6e/badge)](https://www.skillsdirectory.com/skills/ibragimov-oasis-sparc-methodology-d4cc4c6e)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: sparc-methodology
description: >
  SPARC development workflow (Specification, Pseudocode, Architecture, Refinement, Completion).
  Use when: new features, complex implementations, architectural changes.
  Skip when: simple fixes, documentation, configuration.
tags:
  - domain/orchestration
  - artifact/workflow
  - source/core-ruflo
---

# Sparc Methodology Skill

## Purpose
SPARC development workflow (Specification, Pseudocode, Architecture, Refinement, Completion).

## When to Trigger
- new features
- complex implementations
- architectural changes

## When to Skip
- simple fixes
- documentation
- configuration

## Commands

### Specification Phase
Define requirements and acceptance criteria

```bash
npx @claude-flow/cli hooks route --task "specification: [requirements]"
```

### Architecture Phase
Design system structure

```bash
npx @claude-flow/cli hooks route --task "architecture: [design]"
```



## Best Practices
1. Check memory for existing patterns before starting
2. Use hierarchical topology for coordination
3. Store successful patterns after completion
4. Document any new learnings

## 🔗 Связи

- [[MOC - Orchestration]] — Orchestration hub
- [[orchestration/ruflo]] — RuFlo
- [[000 - Map of Maps]] — Map of Maps

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…