SPARC Architecture + Implementation

Run Phases 2 and 3 of the SPARC methodology: translate a verified specification into robust pseudocode, define bounded contexts and module boundaries, produce API contracts, and optionally implement and test the resulting code.

Capabilities

• Create language-agnostic pseudocode covering happy path and edge cases
• Define core data structures with type annotations and algorithmic complexity notes
• Design bounded contexts, aggregates, and domain events (DDD patterns)
• Produce API request/response schemas, error formats, and versioning guidance
• Plan directory/module structure and dependency rules to avoid circular imports
• Recommend persistence, caching, messaging, and infra patterns
• Store artifacts to project memory and record trajectory steps for traceability

Typical invocation

• After the Specification phase (Phase 1) is complete and gated
• Provide feature identifier / spec location; the skill retrieves spec and phase state, then emits pseudocode and architecture artifacts

Output artifacts

• Pseudocode document (algorithms, control flow, complexity)
• Architecture decision record (bounded contexts, API contracts, module layout, infra plan)
• Keys stored in memory: pseudo-{feature-slug}, arch-{feature-slug}