sparc-implement

Generates pseudocode, architecture contracts, and implementation code for SPARC phases 2 and 3.

70.1k|8.4k|Updated Jun 2, 2025
One-click install
npx skills add https://github.com/ruvnet/claude-flow --skill sparc-implement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sparc-implement
Source: https://github.com/ruvnet/claude-flow/tree/main/plugins/ruflo-sparc/skills/sparc-implement
Command: npx skills add https://github.com/ruvnet/claude-flow --skill sparc-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It bridges the gap between a written specification and working code by guiding the SPARC Pseudocode and Architecture phases, so design decisions, module boundaries, and API contracts are documented before implementation begins.

Core Features & Use Cases

  • Pseudocode Design: Writes language-agnostic algorithms for each acceptance criterion, including data structures, control flow, error paths, and complexity annotations.
  • Architecture Design: Defines bounded contexts, aggregate roots, API contracts with TypeScript interfaces, module boundaries, and infrastructure strategy following DDD patterns.
  • Guided Implementation: Creates files following the defined module structure, implements interfaces first, and writes unit tests alongside the code.
  • Use Case: After completing a SPARC specification for a new feature, run this skill to produce the pseudocode and architecture artifacts, store them in shared memory, and begin TDD-style implementation.

Quick Start

Ask the agent to run the SPARC pseudocode and architecture phases for your feature and then start implementing the code with tests.

Frequently Asked Questions about sparc-implement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run the SPARC pseudocode and architecture phases?

Invoke this skill after the SPARC specification phase is complete and its gate passed. It retrieves the spec from memory, writes pseudocode per acceptance criterion, designs bounded contexts and API contracts, then stores both artifacts in the sparc-phases namespace.

What is the SPARC methodology for software development?

SPARC is a phased development workflow covering Specification, Pseudocode, Architecture, Refinement, and Completion. This skill handles phases 2 and 3 together because algorithm design and module boundaries inform each other.

Does this skill write actual production code or only design documents?

It does both. After storing pseudocode and architecture artifacts, it can create files following the defined module structure, implement interfaces first, write core logic from the pseudocode, and add unit tests.

What architecture patterns does the skill use for module design?

It applies Domain-Driven Design patterns: bounded contexts, aggregate roots, value objects, domain events, and dependency direction rules. API contracts are specified as TypeScript interfaces with error codes and versioning strategy.

When should I not use the SPARC phased approach?

Avoid it for trivial scripts, quick prototypes, or exploratory changes where upfront specification and architecture artifacts add overhead without benefit. It suits features with clear acceptance criteria and multiple modules.