$npx -y skills add DNYoussef/context-cascade --skill when-using-sparc-methodology-use-sparc-workflow/*============================================================================*/ /* SKILL SKILL :: VERILINGUA x VERIX EDITION */ /*============================================================================*/
| 1 | /*============================================================================*/ |
| 2 | /* SKILL SKILL :: VERILINGUA x VERIX EDITION */ |
| 3 | /*============================================================================*/ |
| 4 | |
| 5 | --- |
| 6 | name: skill |
| 7 | version: 1.0.0 |
| 8 | description: | |
| 9 | [assert|neutral] skill skill for orchestration workflows [ground:given] [conf:0.95] [state:confirmed] |
| 10 | category: orchestration |
| 11 | tags: |
| 12 | - general |
| 13 | author: system |
| 14 | cognitive_frame: |
| 15 | primary: aspectual |
| 16 | goal_analysis: |
| 17 | first_order: "Execute skill workflow" |
| 18 | second_order: "Ensure quality and consistency" |
| 19 | third_order: "Enable systematic orchestration processes" |
| 20 | --- |
| 21 | |
| 22 | /*----------------------------------------------------------------------------*/ |
| 23 | /* S0 META-IDENTITY */ |
| 24 | /*----------------------------------------------------------------------------*/ |
| 25 | |
| 26 | [define|neutral] SKILL := { |
| 27 | name: "skill", |
| 28 | category: "orchestration", |
| 29 | version: "1.0.0", |
| 30 | layer: L1 |
| 31 | } [ground:given] [conf:1.0] [state:confirmed] |
| 32 | |
| 33 | /*----------------------------------------------------------------------------*/ |
| 34 | /* S1 COGNITIVE FRAME */ |
| 35 | /*----------------------------------------------------------------------------*/ |
| 36 | |
| 37 | [define|neutral] COGNITIVE_FRAME := { |
| 38 | frame: "Aspectual", |
| 39 | source: "Russian", |
| 40 | force: "Complete or ongoing?" |
| 41 | } [ground:cognitive-science] [conf:0.92] [state:confirmed] |
| 42 | |
| 43 | ## Kanitsal Cerceve (Evidential Frame Activation) |
| 44 | Kaynak dogrulama modu etkin. |
| 45 | |
| 46 | /*----------------------------------------------------------------------------*/ |
| 47 | /* S2 TRIGGER CONDITIONS */ |
| 48 | /*----------------------------------------------------------------------------*/ |
| 49 | |
| 50 | [define|neutral] TRIGGER_POSITIVE := { |
| 51 | keywords: ["skill", "orchestration", "workflow"], |
| 52 | context: "user needs skill capability" |
| 53 | } [ground:given] [conf:1.0] [state:confirmed] |
| 54 | |
| 55 | /*----------------------------------------------------------------------------*/ |
| 56 | /* S3 CORE CONTENT */ |
| 57 | /*----------------------------------------------------------------------------*/ |
| 58 | |
| 59 | # When Using SPARC Methodology Use SPARC Workflow |
| 60 | |
| 61 | ## Kanitsal Cerceve (Evidential Frame Activation) |
| 62 | Kaynak dogrulama modu etkin. |
| 63 | |
| 64 | |
| 65 | |
| 66 | --- |
| 67 | name: when-using-sparc-methodology-use-sparc-workflow |
| 68 | trigger: "when user requests SPARC methodology, systematic development, or TDD workflow" |
| 69 | description: "Complete SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) methodology workflow with multi-agent coordination for systematic test-driven development" |
| 70 | version: 2.0.0 |
| 71 | author: Base Template Generator |
| 72 | category: methodology |
| 73 | tags: |
| 74 | - sparc |
| 75 | - methodology |
| 76 | - tdd |
| 77 | - systematic-development |
| 78 | - multi-phase |
| 79 | agents: |
| 80 | - researcher (specification) |
| 81 | - planner (pseudocode) |
| 82 | - system-architect (architecture) |
| 83 | - coder (refinement) |
| 84 | - tester (validation) |
| 85 | - reviewer (quality) |
| 86 | - api-docs (documentation) |
| 87 | coordinator: hierarchical-coordinator |
| 88 | memory_patterns: |
| 89 | - swarm/sparc/specification |
| 90 | - swarm/sparc/pseudocode |
| 91 | - swarm/sparc/architecture |
| 92 | - swarm/sparc/refinement |
| 93 | - swarm/sparc/completion |
| 94 | success_criteria: |
| 95 | - Detailed specification documented |
| 96 | - Pseudocode algorithm designed |
| 97 | - System architecture defined |
| 98 | - Implementation refined through TDD |
| 99 | - All tests passing with ≥90% coverage |
| 100 | - Integration complete and validated |
| 101 | - Comprehensive documentation generated |
| 102 | --- |
| 103 | |
| 104 | ## Trigger Conditions |
| 105 | |
| 106 | Use this skill when: |
| 107 | - User requests SPARC methodology application |
| 108 | - Systematic development workflow needed |
| 109 | - Test-driven development (TDD) approach required |
| 110 | - Complex feature requiring phased approach |
| 111 | - Architecture-first development desired |
| 112 | - Quality gates and validation at each phase needed |
| 113 | - Comprehensive documentation required |
| 114 | - Multi-agent coordinated development |
| 115 | |
| 116 | ## Skill Overview |
| 117 | |
| 118 | SPARC is a systematic development methodology with 5 phases: Specification (requirements), Pseudocode (algorithm design), Architecture (system design), Refinement (TDD implementation), and Completion (integration & documentation). This skill orchestrates all phases with specialized agents coordinating through hierarchical topology and shared memory. |
| 119 | |
| 120 | ## SPARC Methodology Overview |
| 121 | |
| 122 | **S** - Specification: Capture requirements and define success criteria |
| 123 | **P** - Pseudocode: Design algorithm and logic flow |
| 124 | **A** - Architecture: Design system structure and components |
| 125 | **R** - Refinement: Implement through TDD with iterative improvement |
| 126 | **C** - Completion: Integration, validation, and documentation |
| 127 | |
| 128 | ## 7-Phase Skill-Forge Methodology |
| 129 | |
| 130 | ### Phase 1: Specification (Requirements Analysis) |
| 131 | |
| 132 | **Objective**: Capture comprehensive requirements and define success criteria |
| 133 | |
| 134 | **Agent**: `researcher` (specification specialist) |
| 135 | |
| 136 | **Activities**: |
| 137 | - Gather and analyze user requirements |
| 138 | - Define functional and non-functional requirements |
| 139 | - Identify constraints and dependencies |
| 140 | - |