feature-dev-complete
starsforks
How to install feature-dev-complete?
dnyoussef/context-cascade/feature-dev-complete
$npx -y skills add DNYoussef/context-cascade --skill feature-dev-complete/*============================================================================*/ /* FEATURE-DEV-COMPLETE SKILL :: VERILINGUA x VERIX EDITION */ /*============================================================================*/
SKILL.md
| 1 | /*============================================================================*/ |
| 2 | /* FEATURE-DEV-COMPLETE SKILL :: VERILINGUA x VERIX EDITION */ |
| 3 | /*============================================================================*/ |
| 4 | |
| 5 | --- |
| 6 | name: feature-dev-complete |
| 7 | version: 1.1.0 |
| 8 | description: | |
| 9 | [assert|neutral] Complete feature development lifecycle from research to deployment. Uses Gemini Search for best practices, architecture design, Codex prototyping, comprehensive testing, and documentation generation. [ground:given] [conf:0.95] [state:confirmed] |
| 10 | category: delivery |
| 11 | tags: |
| 12 | - feature |
| 13 | - development |
| 14 | - lifecycle |
| 15 | - multi-model |
| 16 | - essential |
| 17 | author: ruv |
| 18 | cognitive_frame: |
| 19 | primary: evidential |
| 20 | goal_analysis: |
| 21 | first_order: "Execute feature-dev-complete workflow" |
| 22 | second_order: "Ensure quality and consistency" |
| 23 | third_order: "Enable systematic delivery processes" |
| 24 | --- |
| 25 | |
| 26 | /*----------------------------------------------------------------------------*/ |
| 27 | /* S0 META-IDENTITY */ |
| 28 | /*----------------------------------------------------------------------------*/ |
| 29 | |
| 30 | [define|neutral] SKILL := { |
| 31 | name: "feature-dev-complete", |
| 32 | category: "delivery", |
| 33 | version: "1.1.0", |
| 34 | layer: L1 |
| 35 | } [ground:given] [conf:1.0] [state:confirmed] |
| 36 | |
| 37 | /*----------------------------------------------------------------------------*/ |
| 38 | /* S1 COGNITIVE FRAME */ |
| 39 | /*----------------------------------------------------------------------------*/ |
| 40 | |
| 41 | [define|neutral] COGNITIVE_FRAME := { |
| 42 | frame: "Evidential", |
| 43 | source: "Turkish", |
| 44 | force: "How do you know?" |
| 45 | } [ground:cognitive-science] [conf:0.92] [state:confirmed] |
| 46 | |
| 47 | ## Kanitsal Cerceve (Evidential Frame Activation) |
| 48 | Kaynak dogrulama modu etkin. |
| 49 | |
| 50 | /*----------------------------------------------------------------------------*/ |
| 51 | /* S2 TRIGGER CONDITIONS */ |
| 52 | /*----------------------------------------------------------------------------*/ |
| 53 | |
| 54 | [define|neutral] TRIGGER_POSITIVE := { |
| 55 | keywords: ["feature-dev-complete", "delivery", "workflow"], |
| 56 | context: "user needs feature-dev-complete capability" |
| 57 | } [ground:given] [conf:1.0] [state:confirmed] |
| 58 | |
| 59 | /*----------------------------------------------------------------------------*/ |
| 60 | /* S3 CORE CONTENT */ |
| 61 | /*----------------------------------------------------------------------------*/ |
| 62 | |
| 63 | # Feature Development Complete |
| 64 | |
| 65 | ## Kanitsal Cerceve (Evidential Frame Activation) |
| 66 | Kaynak dogrulama modu etkin. |
| 67 | |
| 68 | |
| 69 | |
| 70 | ## Aspektual'naya Ramka Aktivatsiya (Aspectual State Tracking) |
| 71 | |
| 72 | Kazhdyy etap razvertyvaniya (Each stage of deployment): |
| 73 | |
| 74 | ### Tipy Sostoyaniya (State Types) |
| 75 | |
| 76 | - **[SV:COMPLETED]** Polnost'yu zaversheno - Stage complete, move to next |
| 77 | - **[NSV:IN_PROGRESS]** V protsesse - Stage active, work ongoing |
| 78 | - **[BLOCKED]** Ozhidaet zavisimosti - Waiting for dependency |
| 79 | - **[INITIATED]** Nachato - Stage started, not yet in progress |
| 80 | |
| 81 | ### 12-Stage State Markers |
| 82 | |
| 83 | Track each stage with explicit state markers: |
| 84 | |
| 85 | 1. **Stage 1 [RESEARCH]**: [SV|NSV|BLOCKED|INITIATED] |
| 86 | 2. **Stage 2 [CODEBASE_ANALYSIS]**: [SV|NSV|BLOCKED|INITIATED] |
| 87 | 3. **Stage 3 [SWARM_INIT]**: [SV|NSV|BLOCKED|INITIATED] |
| 88 | 4. **Stage 4 [ARCHITECTURE]**: [SV|NSV|BLOCKED|INITIATED] |
| 89 | 5. **Stage 5 [DIAGRAMS]**: [SV|NSV|BLOCKED|INITIATED] |
| 90 | 6. **Stage 6 [PROTOTYPE]**: [SV|NSV|BLOCKED|INITIATED] |
| 91 | 7. **Stage 7 [THEATER_DETECTION]**: [SV|NSV|BLOCKED|INITIATED] |
| 92 | 8. **Stage 8 [TESTING]**: [SV|NSV|BLOCKED|INITIATED] |
| 93 | 9. **Stage 9 [STYLE_POLISH]**: [SV|NSV|BLOCKED|INITIATED] |
| 94 | 10. **Stage 10 [SECURITY]**: [SV|NSV|BLOCKED|INITIATED] |
| 95 | 11. **Stage 11 [DOCUMENTATION]**: [SV|NSV|BLOCKED|INITIATED] |
| 96 | 12. **Stage 12 [PRODUCTION_READY]**: [SV|NSV|BLOCKED|INITIATED] |
| 97 | |
| 98 | ### State Transition Rules |
| 99 | |
| 100 | **Transition Protocols**: |
| 101 | - **[NSV->SV]**: All acceptance criteria met, tests passing, artifacts complete |
| 102 | - **[SV->NSV]**: Regression detected, failed tests, reopened for fixes |
| 103 | - **[*->BLOCKED]**: Missing dependency, external blocker, prerequisite incomplete |
| 104 | - **[BLOCKED->NSV]**: Blocker resolved, dependency met, work can resume |
| 105 | - **[INITIATED->NSV]**: Work has begun, active development underway |
| 106 | |
| 107 | **Validation Checkpoints**: |
| 108 | Each transition requires evidence: |
| 109 | - Test results (for TESTING stage) |
| 110 | - Coverage reports (for quality gates) |
| 111 | - Security scan output (for SECURITY stage) |
| 112 | - Artifact existence (for DIAGRAMS, DOCUMENTATION) |
| 113 | |
| 114 | ## Keigo Wakugumi (Hierarchical Work Breakdown) |
| 115 | |
| 116 | ### Work Structure Hierarchy |
| 117 | |
| 118 | ``` |
| 119 | EPIC: [Feature Name] |
| 120 | | |
| 121 | +-- STORY: User story 1 (Business value) |
| 122 | | |
| 123 | +-- TASK: Implementation task 1 |
| 124 | | |
| 125 | +-- SUBTASK: Atomic work item 1.1 |
| 126 | +-- SUBTASK: Atomic work item 1.2 |
| 127 | | |
| 128 | +-- TASK: Implementation task 2 |
| 129 | | |
| 130 | +-- SUBTASK: Atomic work item 2.1 |
| 131 | | |
| 132 | +-- STORY: User story 2 (Business value) |
| 133 | | |
| 134 | +-- TASK: Implementation task 3 |
| 135 | ``` |
| 136 | |
| 137 | ### Hierarchy Levels Explained |
| 138 | |
| 139 | 1. **EPIC |
People who liked this also viewed
6 picksType
- hyperframes-cliUse the HyperFrames CLI development loop: init, add, catalog, capture, lint, check, snapshot, compare, grade-compare, preview, play, present, beats, keyframes, single or batch render, publish, cloud, SkillsJul 2026
- request-refactor-planSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- analyze-projectRigor Analyze / Rigor Audit read-only skill for deep learning research repositories. Use when the user wants to read and understand a repository, inspect model structure and training or inference entrSkillsMay 2026
- explore-codeRigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated braSkillsMay 2026
- ubiquitous-languageSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- scaffold-exercisesSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
