diff --git a/default/skills/brainstorming/SKILL.md b/default/skills/brainstorming/SKILL.md index 8cf4ed7d..f611cfa1 100644 --- a/default/skills/brainstorming/SKILL.md +++ b/default/skills/brainstorming/SKILL.md @@ -1,25 +1,25 @@ --- -name: ring:brainstorming +name: brainstorming description: | Socratic design refinement - transforms rough ideas into validated designs through structured questioning, alternative exploration, and incremental validation. - -trigger: | - - New feature or product idea (requirements unclear) - - User says "plan", "design", or "architect" something - - Multiple approaches seem possible - - Design hasn't been validated by user - -skip_when: | - - Design already complete and validated → use ring:writing-plans - - Have detailed plan ready to execute → use ring:executing-plans - - Just need task breakdown from existing design → use ring:writing-plans - -sequence: - before: [ring:writing-plans, ring:using-git-worktrees] - -related: - similar: [ring:writing-plans] +metadata: + related: + similar: + - ring:writing-plans + sequence: + before: + - ring:writing-plans + - ring:using-git-worktrees + skip_when: | + - Design already complete and validated → use ring:writing-plans + - Have detailed plan ready to execute → use ring:executing-plans + - Just need task breakdown from existing design → use ring:writing-plans + trigger: | + - New feature or product idea (requirements unclear) + - User says "plan", "design", or "architect" something + - Multiple approaches seem possible + - Design hasn't been validated by user --- # Brainstorming Ideas Into Designs diff --git a/default/skills/drawing-diagrams/SKILL.md b/default/skills/drawing-diagrams/SKILL.md index 00a32356..68b7229c 100644 --- a/default/skills/drawing-diagrams/SKILL.md +++ b/default/skills/drawing-diagrams/SKILL.md @@ -1,9 +1,12 @@ --- name: drawing-diagrams -description: Generate Mermaid diagrams from context and open them in mermaid.live in the browser. Use when the user asks for a diagram, visualization, flowchart, sequence diagram, ER diagram, or any visual representation of code, architecture, or processes. Produces lightweight, shareable mermaid.live URLs that open in the browser for interactive editing. +description: Generate Mermaid diagrams from context and open them in mermaid.live in the browser. Use when the user asks for a diagram, visualization, flowchart, sequence diagram, ER diagram, or any visual + representation of code, architecture, or processes. Produces lightweight, shareable mermaid.live URLs that open in the browser for interactive editing. license: MIT compatibility: Requires Python 3 (standard library only) and a browser. Uses `open` on macOS; Linux users need `xdg-open`. -skip_when: The user needs a rich, branded, or styled HTML visualization (use ring:visual-explainer instead). This skill produces shareable mermaid.live URLs; visual-explainer produces self-contained Lerian-branded HTML files. +metadata: + skip_when: The user needs a rich, branded, or styled HTML visualization (use ring:visual-explainer instead). This skill produces shareable mermaid.live URLs; visual-explainer produces self-contained Lerian-branded + HTML files. --- # Mermaid Live Diagram Generator diff --git a/default/skills/executing-plans/SKILL.md b/default/skills/executing-plans/SKILL.md index 85f98339..26384743 100644 --- a/default/skills/executing-plans/SKILL.md +++ b/default/skills/executing-plans/SKILL.md @@ -1,24 +1,24 @@ --- -name: ring:executing-plans +name: executing-plans description: | Controlled plan execution with human review checkpoints - loads plan, executes in batches, pauses for feedback. Supports one-go (autonomous) or batch modes. - -trigger: | - - Have a plan file ready to execute - - Want human review between task batches - - Need structured checkpoints during implementation - -skip_when: | - - Same session with independent tasks → use ring:subagent-driven-development - - No plan exists → use ring:writing-plans first - - Plan needs revision → use ring:brainstorming first - -sequence: - after: [ring:writing-plans, ring:pre-dev-task-breakdown] - -related: - similar: [ring:subagent-driven-development] +metadata: + related: + similar: + - ring:subagent-driven-development + sequence: + after: + - ring:writing-plans + - ring:pre-dev-task-breakdown + skip_when: | + - Same session with independent tasks → use ring:subagent-driven-development + - No plan exists → use ring:writing-plans first + - Plan needs revision → use ring:brainstorming first + trigger: | + - Have a plan file ready to execute + - Want human review between task batches + - Need structured checkpoints during implementation --- # Executing Plans diff --git a/default/skills/exploring-codebase/SKILL.md b/default/skills/exploring-codebase/SKILL.md index 68fb3153..13db2e4a 100644 --- a/default/skills/exploring-codebase/SKILL.md +++ b/default/skills/exploring-codebase/SKILL.md @@ -1,32 +1,35 @@ --- -name: ring:exploring-codebase +name: exploring-codebase description: | Autonomous two-phase codebase exploration - first discovers natural perspectives (layers, components, boundaries), then dispatches adaptive deep-dive explorers based on what was discovered. Synthesizes findings into actionable insights. - -trigger: | - - Need to understand how a feature/system works across the codebase - - Starting work on unfamiliar codebase or component - - Planning changes that span multiple layers/components - - User asks "how does X work?" for non-trivial X - - Need architecture understanding before implementation - -skip_when: | - - Pure reference lookup (function signature, type definition) - - Checking if specific file exists (yes/no question) - - Reading error message from known file location - - WARNING: These are NOT valid skip reasons: - - "I already know the architecture" → Prior knowledge is incomplete - - "Simple question about location" → Location without context is incomplete - - "Production emergency, no time" → High stakes demand MORE rigor - - "Colleague told me structure" → High-level ≠ implementation details - -related: - similar: [dispatching-parallel-agents, systematic-debugging] - sequence_after: [brainstorming] - sequence_before: [ring:writing-plans, ring:executing-plans] +metadata: + related: + similar: + - dispatching-parallel-agents + - systematic-debugging + sequence_after: + - brainstorming + sequence_before: + - ring:writing-plans + - ring:executing-plans + skip_when: | + - Pure reference lookup (function signature, type definition) + - Checking if specific file exists (yes/no question) + - Reading error message from known file location + + WARNING: These are NOT valid skip reasons: + - "I already know the architecture" → Prior knowledge is incomplete + - "Simple question about location" → Location without context is incomplete + - "Production emergency, no time" → High stakes demand MORE rigor + - "Colleague told me structure" → High-level ≠ implementation details + trigger: | + - Need to understand how a feature/system works across the codebase + - Starting work on unfamiliar codebase or component + - Planning changes that span multiple layers/components + - User asks "how does X work?" for non-trivial X + - Need architecture understanding before implementation --- # Autonomous Two-Phase Codebase Exploration diff --git a/default/skills/gandalf-webhook/SKILL.md b/default/skills/gandalf-webhook/SKILL.md index aa90044c..6856b8e3 100644 --- a/default/skills/gandalf-webhook/SKILL.md +++ b/default/skills/gandalf-webhook/SKILL.md @@ -1,11 +1,9 @@ --- -name: ring:gandalf-webhook +name: gandalf-webhook description: Send tasks to Gandalf (AI team member) via webhook and get responses back. Publish to Alfarrábio, send Slack notifications, ask for business context, and more. -user_invocable: true -allowed-tools: - - Bash - - Read - - Write +allowed-tools: Bash, Read, Write +metadata: + user_invocable: true --- # Gandalf Webhook diff --git a/default/skills/git-commit/SKILL.md b/default/skills/git-commit/SKILL.md index cad21808..388c56ed 100644 --- a/default/skills/git-commit/SKILL.md +++ b/default/skills/git-commit/SKILL.md @@ -1,13 +1,9 @@ --- -name: ring:git-commit +name: git-commit description: Smart commit organization with atomic grouping, conventional commits, and trailer management -user_invocable: false -allowed-tools: - - Bash - - Read - - Glob - - Grep - - AskUserQuestion +allowed-tools: Bash, Read, Glob, Grep, AskUserQuestion +metadata: + user_invocable: false --- Analyze changes, group them into coherent atomic commits, and create signed commits following repository conventions. This skill transforms a messy working directory into a clean, logical commit history. diff --git a/default/skills/interviewing-user/SKILL.md b/default/skills/interviewing-user/SKILL.md index b1a27413..58746763 100644 --- a/default/skills/interviewing-user/SKILL.md +++ b/default/skills/interviewing-user/SKILL.md @@ -1,29 +1,30 @@ --- -name: ring:interviewing-user +name: interviewing-user description: | Proactive requirements gathering - systematically interviews the user to uncover ambiguities, preferences, and constraints BEFORE implementation begins. - -trigger: | - - User invokes /ring:interview-me command - - Claude detects significant ambiguity in requirements - - Multiple valid implementation paths exist with no clear winner - - User says "interview me", "ask me questions", "clarify with me" - - Task involves architecture decisions without clear direction - -skip_when: | - - Requirements are already crystal clear - - User has provided detailed specifications - - Following an existing plan with explicit instructions - - Doubt can be resolved via doubt-triggered-questions (single question) - -sequence: - before: [brainstorming, ring:writing-plans] - after: [] - -related: - similar: [brainstorming] - uses: [doubt-triggered-questions] +metadata: + related: + similar: + - brainstorming + uses: + - doubt-triggered-questions + sequence: + before: + - brainstorming + - ring:writing-plans + after: [] + skip_when: | + - Requirements are already crystal clear + - User has provided detailed specifications + - Following an existing plan with explicit instructions + - Doubt can be resolved via doubt-triggered-questions (single question) + trigger: | + - User invokes /ring:interview-me command + - Claude detects significant ambiguity in requirements + - Multiple valid implementation paths exist with no clear winner + - User says "interview me", "ask me questions", "clarify with me" + - Task involves architecture decisions without clear direction --- # Interviewing User for Requirements diff --git a/default/skills/linting-codebase/SKILL.md b/default/skills/linting-codebase/SKILL.md index 2bcbc867..d34ba255 100644 --- a/default/skills/linting-codebase/SKILL.md +++ b/default/skills/linting-codebase/SKILL.md @@ -1,18 +1,17 @@ --- -name: ring:linting-codebase +name: linting-codebase description: | Parallel lint fixing pattern - runs lint checks, groups issues into independent streams, and dispatches AI agents to fix all issues until the codebase is clean. - -trigger: | - - User runs /ring:lint command - - Codebase has lint issues that need fixing - - Multiple lint errors across different files/components - -skip_when: | - - Single lint error → fix directly without agent dispatch - - Lint already passes → nothing to do - - User only wants to see lint output, not fix +metadata: + skip_when: |- + - Single lint error → fix directly without agent dispatch + - Lint already passes → nothing to do + - User only wants to see lint output, not fix + trigger: | + - User runs /ring:lint command + - Codebase has lint issues that need fixing + - Multiple lint errors across different files/components --- # Linting Codebase diff --git a/default/skills/production-readiness-audit/SKILL.md b/default/skills/production-readiness-audit/SKILL.md index 8fded501..bd214b46 100644 --- a/default/skills/production-readiness-audit/SKILL.md +++ b/default/skills/production-readiness-audit/SKILL.md @@ -1,10 +1,15 @@ --- -name: ring:production-readiness-audit -title: Production Readiness Audit -category: operations -tier: advanced -description: Comprehensive Ring-standards-aligned 44-dimension production readiness audit. Detects project stack, loads Ring standards via WebFetch, and runs in batches of 10 explorers appending incrementally to a single report file. Categories - Structure (pagination, errors, routes, bootstrap, runtime, core deps, naming, domain modeling, nil-safety, api-versioning, resource-leaks), Security (auth, IDOR, SQL, validation, secret-scanning, data-encryption, multi-tenant, rate-limiting, cors), Operations (telemetry, health, config, connections, logging, resilience, graceful-degradation), Quality (idempotency, docs, debt, testing, dependencies, performance, concurrency, migrations, linting, caching), Infrastructure (containers, hardening, cicd, async, makefile, license). Produces scored report (0-430, max 440 with multi-tenant) with severity ratings and standards cross-reference. +name: production-readiness-audit +description: Comprehensive Ring-standards-aligned 44-dimension production readiness audit. Detects project stack, loads Ring standards via WebFetch, and runs in batches of 10 explorers appending incrementally + to a single report file. Categories - Structure (pagination, errors, routes, bootstrap, runtime, core deps, naming, domain modeling, nil-safety, api-versioning, resource-leaks), Security (auth, IDOR, + SQL, validation, secret-scanning, data-encryption, multi-tenant, rate-limiting, cors), Operations (telemetry, health, config, connections, logging, resilience, graceful-degradation), Quality (idempotency, + docs, debt, testing, dependencies, performance, concurrency, migrations, linting, caching), Infrastructure (containers, hardening, cicd, async, makefile, license). Produces scored report (0-430, max 440 + with multi-tenant) with severity ratings and standards cross-reference. allowed-tools: Task, Read, Glob, Grep, Write, TodoWrite, WebFetch +metadata: + category: operations + tier: advanced + title: Production Readiness Audit --- # Production Readiness Audit diff --git a/default/skills/release-guide-info/SKILL.md b/default/skills/release-guide-info/SKILL.md index 252b7fbc..bdd53684 100644 --- a/default/skills/release-guide-info/SKILL.md +++ b/default/skills/release-guide-info/SKILL.md @@ -1,81 +1,92 @@ --- -name: ring:release-guide-info -version: 1.2.0 +name: release-guide-info description: | Generate Ops Update Guide from Git Diff. Produces internal Operations-facing update/migration guides based on git diff analysis. Supports STRICT_NO_TOUCH (default) and TEMP_CLONE_FOR_FRESH_REFS modes. Includes tag auto-detection and commit log analysis. - -trigger: | - - Preparing to release a new version - - Need to document what changed between refs - - Creating operational update guide - - Communicating version updates to Ops team - - "Generate ops guide from main to HEAD" - - "Generate release guide for " - -skip_when: | - - No git repository available - - Single file change (too small for formal guide) - - Customer-facing release notes only (use simpler template) - -input_schema: - BASE_REF: - type: string - required: true - description: Starting point (branch, tag, or SHA) - examples: ["main", "release/v3.4.x", "v1.0.0"] - TARGET_REF: - type: string - required: true - description: Ending point (branch, tag, or SHA) - examples: ["HEAD", "feature/foo", "v1.1.0"] - VERSION: - type: string - required: false - description: Version number for the release (auto-detected from tags if not provided) - examples: ["v2.0.0", "1.5.0", "2025.01"] - LANGUAGE: - type: enum - required: false - default: "en" - values: ["en", "pt-br", "both"] - description: Output language(s) for the guide - MODE: - type: enum - required: false - default: "STRICT_NO_TOUCH" - values: ["STRICT_NO_TOUCH", "TEMP_CLONE_FOR_FRESH_REFS"] - description: Git execution mode - -output_schema: - files: - type: array - description: List of generated guide files - items: - path: string - language: string - summary: - type: object - description: Quick summary of changes - properties: - features: number - bug_fixes: number - improvements: number - breaking_changes: number - version: - type: string - description: Version number (provided or auto-detected) - refs: - type: object - properties: - base: string - target: string - base_sha: string - target_sha: string - -related: - complementary: [finishing-a-development-branch] +metadata: + input_schema: + BASE_REF: + type: string + required: true + description: Starting point (branch, tag, or SHA) + examples: + - main + - release/v3.4.x + - v1.0.0 + TARGET_REF: + type: string + required: true + description: Ending point (branch, tag, or SHA) + examples: + - HEAD + - feature/foo + - v1.1.0 + VERSION: + type: string + required: false + description: Version number for the release (auto-detected from tags if not provided) + examples: + - v2.0.0 + - 1.5.0 + - '2025.01' + LANGUAGE: + type: enum + required: false + default: en + values: + - en + - pt-br + - both + description: Output language(s) for the guide + MODE: + type: enum + required: false + default: STRICT_NO_TOUCH + values: + - STRICT_NO_TOUCH + - TEMP_CLONE_FOR_FRESH_REFS + description: Git execution mode + output_schema: + files: + type: array + description: List of generated guide files + items: + path: string + language: string + summary: + type: object + description: Quick summary of changes + properties: + features: number + bug_fixes: number + improvements: number + breaking_changes: number + version: + type: string + description: Version number (provided or auto-detected) + refs: + type: object + properties: + base: string + target: string + base_sha: string + target_sha: string + related: + complementary: + - finishing-a-development-branch + skip_when: | + - No git repository available + - Single file change (too small for formal guide) + - Customer-facing release notes only (use simpler template) + trigger: | + - Preparing to release a new version + - Need to document what changed between refs + - Creating operational update guide + - Communicating version updates to Ops team + - "Generate ops guide from main to HEAD" + - "Generate release guide for " + version: 1.2.0 --- # Release Guide Info — Ops Update Guide Generator diff --git a/default/skills/requesting-code-review/SKILL.md b/default/skills/requesting-code-review/SKILL.md index dd9be9bf..3e0076c8 100644 --- a/default/skills/requesting-code-review/SKILL.md +++ b/default/skills/requesting-code-review/SKILL.md @@ -1,5 +1,5 @@ --- -name: ring:requesting-code-review +name: requesting-code-review description: | Gate 4 of development cycle - dispatches 7 specialized reviewers (code, business-logic, security, test, nil-safety, consequences, dead-code) in parallel for comprehensive code review feedback. diff --git a/default/skills/session-handoff/SKILL.md b/default/skills/session-handoff/SKILL.md index 2f804b10..16fb027e 100644 --- a/default/skills/session-handoff/SKILL.md +++ b/default/skills/session-handoff/SKILL.md @@ -1,14 +1,9 @@ --- -name: ring:session-handoff +name: session-handoff description: Create handoff documents capturing session state for seamless context-clear and resume -user_invocable: false -allowed-tools: - - EnterPlanMode - - ExitPlanMode - - Write - - Bash - - Read - - Glob +allowed-tools: EnterPlanMode, ExitPlanMode, Write, Bash, Read, Glob +metadata: + user_invocable: false --- # Session Handoff Skill diff --git a/default/skills/systematic-debugging/SKILL.md b/default/skills/systematic-debugging/SKILL.md index 9f24cc97..aaf61dcd 100644 --- a/default/skills/systematic-debugging/SKILL.md +++ b/default/skills/systematic-debugging/SKILL.md @@ -1,22 +1,21 @@ --- -name: ring:systematic-debugging +name: systematic-debugging description: | Four-phase debugging framework - root cause investigation, pattern analysis, hypothesis testing, implementation. Ensures understanding before attempting fixes. - -trigger: | - - Bug reported or test failure observed - - Unexpected behavior or error message - - Root cause unknown - - Previous fix attempt didn't work - -skip_when: | - - Root cause already known → just fix it - - Error deep in call stack, need to trace backward → use root-cause-tracing - - Issue obviously caused by your last change → quick verification first - -related: - complementary: [root-cause-tracing] +metadata: + related: + complementary: + - root-cause-tracing + skip_when: | + - Root cause already known → just fix it + - Error deep in call stack, need to trace backward → use root-cause-tracing + - Issue obviously caused by your last change → quick verification first + trigger: | + - Bug reported or test failure observed + - Unexpected behavior or error message + - Root cause unknown + - Previous fix attempt didn't work --- # Systematic Debugging diff --git a/default/skills/test-driven-development/SKILL.md b/default/skills/test-driven-development/SKILL.md index b0d5abb1..486c0051 100644 --- a/default/skills/test-driven-development/SKILL.md +++ b/default/skills/test-driven-development/SKILL.md @@ -1,71 +1,64 @@ --- -name: ring:test-driven-development +name: test-driven-development description: | RED-GREEN-REFACTOR implementation methodology - write failing test first, minimal implementation to pass, then refactor. Ensures tests verify behavior. - -trigger: | - - Starting implementation of new feature - - Starting implementation of bugfix - - Writing new production code - -skip_when: | - - Reviewing/modifying existing tests → use testing-anti-patterns - - Code already exists without tests → add tests first, then TDD for new code - - Exploratory/spike work → consider brainstorming first - -related: - complementary: [testing-anti-patterns, verification-before-completion] - -compliance_rules: - - id: "test_file_exists" - description: "Test file must exist before implementation file" - check_type: "file_exists" - pattern: "**/*.test.{ts,js,go,py}" - severity: "blocking" - failure_message: "No test file found. Write test first (RED phase)." - - - id: "test_must_fail_first" - description: "Test must produce failure output before implementation" - check_type: "command_output_contains" - command: "npm test 2>&1 || pytest 2>&1 || go test ./... 2>&1" - pattern: "FAIL|Error|failed" - severity: "blocking" - failure_message: "Test does not fail. Write a failing test first (RED phase)." -prerequisites: - - name: "test_framework_installed" - check: "npm list jest 2>/dev/null || npm list vitest 2>/dev/null || which pytest 2>/dev/null || go list ./... 2>&1 | grep -q testing" - failure_message: "No test framework found. Install jest/vitest (JS), pytest (Python), or use Go's built-in testing." - severity: "blocking" - - - name: "can_run_tests" - check: "npm test -- --version 2>/dev/null || pytest --version 2>/dev/null || go test -v 2>&1 | grep -q 'testing:'" - failure_message: "Cannot run tests. Fix test configuration." - severity: "warning" -composition: - works_well_with: - - skill: "ring:systematic-debugging" - when: "test reveals unexpected behavior or bug" - transition: "Pause TDD at current phase, use systematic-debugging to find root cause, return to TDD after fix" - - - skill: "ring:verification-before-completion" - when: "before marking test suite or feature complete" - transition: "Run verification to ensure all tests pass, return to TDD if issues found" - - - skill: "ring:requesting-code-review" - when: "after completing RED-GREEN-REFACTOR cycle for feature" - transition: "Request review before merging, address feedback, mark complete" - - conflicts_with: [] - - typical_workflow: | - 1. Write failing test (RED) - 2. If test reveals unexpected behavior → switch to systematic-debugging - 3. Fix root cause - 4. Return to TDD: minimal implementation (GREEN) - 5. Refactor (REFACTOR) - 6. Run verification-before-completion - 7. Request code review +metadata: + compliance_rules: + - id: test_file_exists + description: Test file must exist before implementation file + check_type: file_exists + pattern: '**/*.test.{ts,js,go,py}' + severity: blocking + failure_message: No test file found. Write test first (RED phase). + - id: test_must_fail_first + description: Test must produce failure output before implementation + check_type: command_output_contains + command: npm test 2>&1 || pytest 2>&1 || go test ./... 2>&1 + pattern: FAIL|Error|failed + severity: blocking + failure_message: Test does not fail. Write a failing test first (RED phase). + composition: + works_well_with: + - skill: ring:systematic-debugging + when: test reveals unexpected behavior or bug + transition: Pause TDD at current phase, use systematic-debugging to find root cause, return to TDD after fix + - skill: ring:verification-before-completion + when: before marking test suite or feature complete + transition: Run verification to ensure all tests pass, return to TDD if issues found + - skill: ring:requesting-code-review + when: after completing RED-GREEN-REFACTOR cycle for feature + transition: Request review before merging, address feedback, mark complete + conflicts_with: [] + typical_workflow: |- + 1. Write failing test (RED) + 2. If test reveals unexpected behavior → switch to systematic-debugging + 3. Fix root cause + 4. Return to TDD: minimal implementation (GREEN) + 5. Refactor (REFACTOR) + 6. Run verification-before-completion + 7. Request code review + prerequisites: + - name: test_framework_installed + check: npm list jest 2>/dev/null || npm list vitest 2>/dev/null || which pytest 2>/dev/null || go list ./... 2>&1 | grep -q testing + failure_message: No test framework found. Install jest/vitest (JS), pytest (Python), or use Go's built-in testing. + severity: blocking + - name: can_run_tests + check: npm test -- --version 2>/dev/null || pytest --version 2>/dev/null || go test -v 2>&1 | grep -q 'testing:' + failure_message: Cannot run tests. Fix test configuration. + severity: warning + related: + complementary: + - testing-anti-patterns + - verification-before-completion + skip_when: | + - Reviewing/modifying existing tests → use testing-anti-patterns + - Code already exists without tests → add tests first, then TDD for new code + - Exploratory/spike work → consider brainstorming first + trigger: | + - Starting implementation of new feature + - Starting implementation of bugfix + - Writing new production code --- # Test-Driven Development (TDD) diff --git a/default/skills/testing-agents-with-subagents/SKILL.md b/default/skills/testing-agents-with-subagents/SKILL.md index 8283c41c..061023fd 100644 --- a/default/skills/testing-agents-with-subagents/SKILL.md +++ b/default/skills/testing-agents-with-subagents/SKILL.md @@ -1,20 +1,19 @@ --- -name: ring:testing-agents-with-subagents +name: testing-agents-with-subagents description: | Agent testing methodology - run agents with test inputs, observe outputs, iterate until outputs are accurate and well-structured. - -trigger: | - - Before deploying a new agent - - After editing an existing agent - - Agent produces structured outputs that must be accurate - -skip_when: | - - Agent is simple passthrough → minimal testing needed - - Agent already tested for this use case - -related: - complementary: [ring:test-driven-development] +metadata: + related: + complementary: + - ring:test-driven-development + skip_when: | + - Agent is simple passthrough → minimal testing needed + - Agent already tested for this use case + trigger: | + - Before deploying a new agent + - After editing an existing agent + - Agent produces structured outputs that must be accurate --- # Testing Agents With Subagents diff --git a/default/skills/testing-anti-patterns/SKILL.md b/default/skills/testing-anti-patterns/SKILL.md index 8c40ffa8..220090f0 100644 --- a/default/skills/testing-anti-patterns/SKILL.md +++ b/default/skills/testing-anti-patterns/SKILL.md @@ -1,21 +1,20 @@ --- -name: ring:testing-anti-patterns +name: testing-anti-patterns description: | Test quality guard - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies. - -trigger: | - - Reviewing or modifying existing tests - - Adding mocks to tests - - Tempted to add test-only methods to production code - - Tests passing but seem to test the wrong things - -skip_when: | - - Writing new tests via TDD → TDD prevents these patterns - - Pure unit tests without mocks → check other quality concerns - -related: - complementary: [ring:test-driven-development] +metadata: + related: + complementary: + - ring:test-driven-development + skip_when: | + - Writing new tests via TDD → TDD prevents these patterns + - Pure unit tests without mocks → check other quality concerns + trigger: | + - Reviewing or modifying existing tests + - Adding mocks to tests + - Tempted to add test-only methods to production code + - Tests passing but seem to test the wrong things --- # Testing Anti-Patterns diff --git a/default/skills/testing-skills-with-subagents/SKILL.md b/default/skills/testing-skills-with-subagents/SKILL.md index da8b67c9..6ffbfebe 100644 --- a/default/skills/testing-skills-with-subagents/SKILL.md +++ b/default/skills/testing-skills-with-subagents/SKILL.md @@ -1,20 +1,20 @@ --- -name: ring:testing-skills-with-subagents +name: testing-skills-with-subagents description: | Skill testing methodology - run scenarios without skill (RED), observe failures, write skill (GREEN), close loopholes (REFACTOR). - -trigger: | - - Before deploying a new skill - - After editing an existing skill - - Skill enforces discipline that could be rationalized away - -skip_when: | - - Pure reference skill → no behavior to test - - No rules that agents have incentive to bypass - -related: - complementary: [ring:writing-skills, ring:test-driven-development] +metadata: + related: + complementary: + - ring:writing-skills + - ring:test-driven-development + skip_when: | + - Pure reference skill → no behavior to test + - No rules that agents have incentive to bypass + trigger: | + - Before deploying a new skill + - After editing an existing skill + - Skill enforces discipline that could be rationalized away --- # Testing Skills With Subagents diff --git a/default/skills/using-git-worktrees/SKILL.md b/default/skills/using-git-worktrees/SKILL.md index 5872525f..3f7bb854 100644 --- a/default/skills/using-git-worktrees/SKILL.md +++ b/default/skills/using-git-worktrees/SKILL.md @@ -1,22 +1,23 @@ --- -name: ring:using-git-worktrees +name: using-git-worktrees description: | Isolated workspace creation - creates git worktrees with smart directory selection and safety verification for parallel feature development. - -trigger: | - - Starting feature that needs isolation from main workspace - - Before executing implementation plan - - Working on multiple features simultaneously - -skip_when: | - - Quick fix in current branch → stay in place - - Already in isolated worktree for this feature → continue - - Repository doesn't use worktrees → use standard branch workflow - -sequence: - after: [brainstorming] - before: [ring:writing-plans, ring:executing-plans] +metadata: + sequence: + after: + - brainstorming + before: + - ring:writing-plans + - ring:executing-plans + skip_when: | + - Quick fix in current branch → stay in place + - Already in isolated worktree for this feature → continue + - Repository doesn't use worktrees → use standard branch workflow + trigger: | + - Starting feature that needs isolation from main workspace + - Before executing implementation plan + - Working on multiple features simultaneously --- # Using Git Worktrees diff --git a/default/skills/using-ring/SKILL.md b/default/skills/using-ring/SKILL.md index 6e4e5c5a..0f853577 100644 --- a/default/skills/using-ring/SKILL.md +++ b/default/skills/using-ring/SKILL.md @@ -1,16 +1,14 @@ --- -name: ring:using-ring +name: using-ring description: | Mandatory orchestrator protocol - establishes ORCHESTRATOR principle (dispatch agents, don't operate directly) and skill discovery workflow for every conversation. - -trigger: | - - Every conversation start (automatic via SessionStart hook) - - Before ANY task (check for applicable skills) - - When tempted to operate tools directly instead of delegating - -skip_when: | - - Never skip - this skill is always mandatory +metadata: + skip_when: '- Never skip - this skill is always mandatory' + trigger: | + - Every conversation start (automatic via SessionStart hook) + - Before ANY task (check for applicable skills) + - When tempted to operate tools directly instead of delegating --- diff --git a/default/skills/visual-explainer/SKILL.md b/default/skills/visual-explainer/SKILL.md index 2f64736d..4a898e2b 100644 --- a/default/skills/visual-explainer/SKILL.md +++ b/default/skills/visual-explainer/SKILL.md @@ -1,11 +1,13 @@ --- -name: ring:visual-explainer -description: Generate beautiful, self-contained HTML pages that visually explain systems, code changes, plans, and data. Use when the user asks for a diagram, architecture overview, diff review, plan review, project recap, comparison table, or any visual explanation of technical concepts. Also use proactively when you are about to render a complex ASCII table (4+ rows or 3+ columns) — present it as a styled HTML page instead. +name: visual-explainer +description: Generate beautiful, self-contained HTML pages that visually explain systems, code changes, plans, and data. Use when the user asks for a diagram, architecture overview, diff review, plan review, + project recap, comparison table, or any visual explanation of technical concepts. Also use proactively when you are about to render a complex ASCII table (4+ rows or 3+ columns) — present it as a styled + HTML page instead. license: MIT compatibility: Requires a browser to view generated HTML files. Optional surf-cli for AI image generation. metadata: author: nicobailon - version: "0.3.0" + version: 0.3.0 --- # Visual Explainer diff --git a/default/skills/writing-plans/SKILL.md b/default/skills/writing-plans/SKILL.md index c23a9516..a953ce63 100644 --- a/default/skills/writing-plans/SKILL.md +++ b/default/skills/writing-plans/SKILL.md @@ -1,25 +1,27 @@ --- -name: ring:writing-plans +name: writing-plans description: | Creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps for engineers with zero codebase context. - -trigger: | - - Design phase complete (brainstorming/PRD/TRD validated) - - Need to create executable task breakdown - - Creating work for other engineers or AI agents - -skip_when: | - - Design not validated → use brainstorming first - - Requirements still unclear → use ring:pre-dev-prd-creation first - - Already have a plan → use ring:executing-plans - -sequence: - after: [brainstorming, ring:pre-dev-trd-creation] - before: [ring:executing-plans, ring:subagent-driven-development] - -related: - similar: [brainstorming] +metadata: + related: + similar: + - brainstorming + sequence: + after: + - brainstorming + - ring:pre-dev-trd-creation + before: + - ring:executing-plans + - ring:subagent-driven-development + skip_when: | + - Design not validated → use brainstorming first + - Requirements still unclear → use ring:pre-dev-prd-creation first + - Already have a plan → use ring:executing-plans + trigger: | + - Design phase complete (brainstorming/PRD/TRD validated) + - Need to create executable task breakdown + - Creating work for other engineers or AI agents --- # Writing Plans diff --git a/default/skills/writing-skills/SKILL.md b/default/skills/writing-skills/SKILL.md index 602e2ef0..78f43339 100644 --- a/default/skills/writing-skills/SKILL.md +++ b/default/skills/writing-skills/SKILL.md @@ -1,20 +1,19 @@ --- -name: ring:writing-skills +name: writing-skills description: | TDD for process documentation - write test cases (pressure scenarios), watch baseline fail, write skill, iterate until bulletproof against rationalization. - -trigger: | - - Creating a new skill - - Editing an existing skill - - Skill needs to resist rationalization under pressure - -skip_when: | - - Writing pure reference skill (API docs) → no rules to test - - Skill has no compliance costs → no rationalization risk - -related: - complementary: [testing-skills-with-subagents] +metadata: + related: + complementary: + - testing-skills-with-subagents + skip_when: | + - Writing pure reference skill (API docs) → no rules to test + - Skill has no compliance costs → no rationalization risk + trigger: | + - Creating a new skill + - Editing an existing skill + - Skill needs to resist rationalization under pressure --- # Writing Skills diff --git a/dev-team/skills/cycle-management/SKILL.md b/dev-team/skills/cycle-management/SKILL.md index a43af121..62e7948c 100644 --- a/dev-team/skills/cycle-management/SKILL.md +++ b/dev-team/skills/cycle-management/SKILL.md @@ -1,14 +1,9 @@ --- -name: ring:cycle-management +name: cycle-management description: Development cycle state management — status reporting and cycle cancellation -user_invocable: false -allowed-tools: - - Read - - Write - - Bash - - Glob - - Grep - - AskUserQuestion +allowed-tools: Read, Write, Bash, Glob, Grep, AskUserQuestion +metadata: + user_invocable: false --- # Cycle Management diff --git a/dev-team/skills/dev-chaos-testing/SKILL.md b/dev-team/skills/dev-chaos-testing/SKILL.md index 96ccf4cb..34671bd3 100644 --- a/dev-team/skills/dev-chaos-testing/SKILL.md +++ b/dev-team/skills/dev-chaos-testing/SKILL.md @@ -1,5 +1,5 @@ --- -name: ring:dev-chaos-testing +name: dev-chaos-testing title: Development cycle chaos testing (Gate 7) category: development-cycle tier: 1 diff --git a/dev-team/skills/dev-cycle-frontend/SKILL.md b/dev-team/skills/dev-cycle-frontend/SKILL.md index 06b4a728..cf02f163 100644 --- a/dev-team/skills/dev-cycle-frontend/SKILL.md +++ b/dev-team/skills/dev-cycle-frontend/SKILL.md @@ -1,41 +1,13 @@ --- -name: ring:dev-cycle-frontend +name: dev-cycle-frontend description: | Frontend development cycle orchestrator with 9 gates. Loads tasks from PM team output or backend handoff and executes through implementation → devops → accessibility → unit testing → visual testing → E2E testing → performance testing → review → validation. - -trigger: | - - Starting a new frontend development cycle with a task file - - Resuming an interrupted frontend development cycle (--resume flag) - - After backend dev cycle completes (consuming handoff) - -prerequisite: | - - Tasks file exists with structured subtasks - - Not already in a specific gate skill execution - -skip_when: | - - "Task is simple" → Simple ≠ risk-free. Execute gates. - - "Tests already pass" → Tests ≠ review. Different concerns. - - "Backend already tested this" → Frontend has different quality concerns. - -sequence: - before: [ring:dev-feedback-loop] - -related: - complementary: [ring:dev-frontend-accessibility, ring:dev-unit-testing, ring:dev-frontend-visual, ring:dev-frontend-e2e, ring:dev-frontend-performance, ring:requesting-code-review, ring:dev-validation, ring:dev-feedback-loop] - -verification: - automated: - - command: "test -f docs/ring:dev-cycle-frontend/current-cycle.json" - description: "State file exists" - success_pattern: "exit 0" - manual: - - "All gates for current task show PASS in state file" - -examples: - - name: "New frontend from backend handoff" - invocation: "/ring:dev-cycle-frontend docs/pre-dev/auth/tasks-frontend.md" +metadata: + examples: + - name: New frontend from backend handoff + invocation: /ring:dev-cycle-frontend docs/pre-dev/auth/tasks-frontend.md expected_flow: | 1. Load tasks with subtasks 2. Detect UI library mode (sindarian-ui or fallback) @@ -43,10 +15,41 @@ examples: 4. Ask user for execution mode 5. Execute Gate 0→1→2→3→4→5→6→7→8 for each task 6. Generate feedback report - - name: "Resume interrupted frontend cycle" - invocation: "/ring:dev-cycle-frontend --resume" - - name: "Direct prompt mode" - invocation: "/ring:dev-cycle-frontend Implement dashboard with transaction list and charts" + - name: Resume interrupted frontend cycle + invocation: /ring:dev-cycle-frontend --resume + - name: Direct prompt mode + invocation: /ring:dev-cycle-frontend Implement dashboard with transaction list and charts + prerequisite: | + - Tasks file exists with structured subtasks + - Not already in a specific gate skill execution + related: + complementary: + - ring:dev-frontend-accessibility + - ring:dev-unit-testing + - ring:dev-frontend-visual + - ring:dev-frontend-e2e + - ring:dev-frontend-performance + - ring:requesting-code-review + - ring:dev-validation + - ring:dev-feedback-loop + sequence: + before: + - ring:dev-feedback-loop + skip_when: | + - "Task is simple" → Simple ≠ risk-free. Execute gates. + - "Tests already pass" → Tests ≠ review. Different concerns. + - "Backend already tested this" → Frontend has different quality concerns. + trigger: | + - Starting a new frontend development cycle with a task file + - Resuming an interrupted frontend development cycle (--resume flag) + - After backend dev cycle completes (consuming handoff) + verification: + automated: + - command: test -f docs/ring:dev-cycle-frontend/current-cycle.json + description: State file exists + success_pattern: exit 0 + manual: + - All gates for current task show PASS in state file --- # Frontend Development Cycle Orchestrator diff --git a/dev-team/skills/dev-cycle/SKILL.md b/dev-team/skills/dev-cycle/SKILL.md index 5248754c..00adfa26 100644 --- a/dev-team/skills/dev-cycle/SKILL.md +++ b/dev-team/skills/dev-cycle/SKILL.md @@ -1,77 +1,80 @@ --- -name: ring:dev-cycle +name: dev-cycle description: | Main orchestrator for the 10-gate development cycle system. Loads tasks/subtasks from PM team output and executes through implementation → devops → SRE → unit testing → fuzz testing → property testing → integration testing (write) → chaos testing (write) → review → validation gates (Gates 0-9), with state persistence and metrics collection. Gates 6-7 (integration/chaos) write and update test code per unit but only execute tests at end of cycle (deferred execution). Multi-tenant dual-mode is implemented during Gate 0 and verified at Gate 0.5G (no separate post-cycle step). - -trigger: | - - Starting a new development cycle with a task file - - Resuming an interrupted development cycle (--resume flag) - - Need structured, gate-based task execution with quality checkpoints - -prerequisite: | - - Tasks file exists with structured subtasks - - Not already in a specific gate skill execution - - Human has not explicitly requested manual workflow - -NOT_skip_when: | - - "Task is simple" → Simple ≠ risk-free. Execute gates. - - "Tests already pass" → Tests ≠ review. Different concerns. - - "Time pressure" → Pressure ≠ permission. Document and proceed. - - "Already did N gates" → Sunk cost is irrelevant. Complete all gates. - -sequence: - before: [ring:dev-feedback-loop] - -related: - complementary: [ring:dev-implementation, ring:dev-devops, ring:dev-sre, ring:dev-unit-testing, ring:requesting-code-review, ring:dev-validation, ring:dev-feedback-loop, ring:dev-delivery-verification] - -verification: - automated: - - command: "test -f docs/ring:dev-cycle/current-cycle.json || test -f docs/ring:dev-refactor/current-cycle.json" - description: "State file exists (ring:dev-cycle or ring:dev-refactor)" - success_pattern: "exit 0" - - command: "cat docs/ring:dev-cycle/current-cycle.json 2>/dev/null || cat docs/ring:dev-refactor/current-cycle.json | jq '.current_gate'" - description: "Current gate is valid" - success_pattern: '[0-5]|0\.5' - manual: - - "All gates for current task show PASS in state file" - - "No tasks have status 'blocked' for more than 3 iterations" - -examples: - - name: "New feature from PM workflow" - invocation: "/ring:dev-cycle docs/pre-dev/auth/tasks.md" +metadata: + NOT_skip_when: | + - "Task is simple" → Simple ≠ risk-free. Execute gates. + - "Tests already pass" → Tests ≠ review. Different concerns. + - "Time pressure" → Pressure ≠ permission. Document and proceed. + - "Already did N gates" → Sunk cost is irrelevant. Complete all gates. + examples: + - name: New feature from PM workflow + invocation: /ring:dev-cycle docs/pre-dev/auth/tasks.md expected_flow: | 1. Load tasks with subtasks from tasks.md 2. Ask user for checkpoint mode (per-task/per-gate/continuous) 3. Execute Gate 0→0.5→1→2→3→4→5→6→7→8→9 for each task sequentially 4. Generate feedback report after completion - - name: "Resume interrupted cycle" - invocation: "/ring:dev-cycle --resume" - expected_state: "Continues from last saved gate in current-cycle.json" - - name: "Execute with per-gate checkpoints" - invocation: "/ring:dev-cycle tasks.md --checkpoint per-gate" + - name: Resume interrupted cycle + invocation: /ring:dev-cycle --resume + expected_state: Continues from last saved gate in current-cycle.json + - name: Execute with per-gate checkpoints + invocation: /ring:dev-cycle tasks.md --checkpoint per-gate expected_flow: | 1. Execute Gate 0, pause for approval 2. User approves, execute Gate 1, pause 3. Continue until all 11 gates complete - - name: "Execute with custom context for agents" - invocation: "/ring:dev-cycle tasks.md \"Focus on error handling. Use existing UserRepository.\"" + - name: Execute with custom context for agents + invocation: /ring:dev-cycle tasks.md "Focus on error handling. Use existing UserRepository." expected_flow: | 1. Load tasks and store custom_prompt in state 2. All agent dispatches include custom instructions as context 3. Custom context visible in execution report - - name: "Instructions-only mode (no tasks file)" - invocation: "/ring:dev-cycle \"Add webhook notification support for account status changes\"" - expected_flow: | + - name: Instructions-only mode (no tasks file) + invocation: /ring:dev-cycle "Add webhook notification support for account status changes" + expected_flow: |- 1. Detect prompt-only mode (no task file provided) 2. Dispatch ring:codebase-explorer to analyze project 3. Generate tasks internally from prompt + codebase analysis 4. Present generated tasks for user confirmation 5. Execute Gate 0→0.5→1→2→3→4→5→6→7→8→9 for each generated task + prerequisite: | + - Tasks file exists with structured subtasks + - Not already in a specific gate skill execution + - Human has not explicitly requested manual workflow + related: + complementary: + - ring:dev-implementation + - ring:dev-devops + - ring:dev-sre + - ring:dev-unit-testing + - ring:requesting-code-review + - ring:dev-validation + - ring:dev-feedback-loop + - ring:dev-delivery-verification + sequence: + before: + - ring:dev-feedback-loop + trigger: | + - Starting a new development cycle with a task file + - Resuming an interrupted development cycle (--resume flag) + - Need structured, gate-based task execution with quality checkpoints + verification: + automated: + - command: test -f docs/ring:dev-cycle/current-cycle.json || test -f docs/ring:dev-refactor/current-cycle.json + description: State file exists (ring:dev-cycle or ring:dev-refactor) + success_pattern: exit 0 + - command: cat docs/ring:dev-cycle/current-cycle.json 2>/dev/null || cat docs/ring:dev-refactor/current-cycle.json | jq '.current_gate' + description: Current gate is valid + success_pattern: '[0-5]|0\.5' + manual: + - All gates for current task show PASS in state file + - No tasks have status 'blocked' for more than 3 iterations --- # Development Cycle Orchestrator diff --git a/dev-team/skills/dev-delivery-verification/SKILL.md b/dev-team/skills/dev-delivery-verification/SKILL.md index 2340ae2c..adda0cea 100644 --- a/dev-team/skills/dev-delivery-verification/SKILL.md +++ b/dev-team/skills/dev-delivery-verification/SKILL.md @@ -1,76 +1,64 @@ --- -name: ring:dev-delivery-verification -version: 1.0.0 +name: dev-delivery-verification description: | Delivery Verification Gate — verifies that what was requested is actually delivered as reachable, integrated code. Not quality review (Gate 8), not test verification (Gate 9) — this gate answers: "Is every requirement from the original task actually functioning in the running application?" Applies to ANY task type: features, refactors, fixes, infrastructure, API endpoints, middleware, business logic, integrations. - -trigger: | - - After Gate 0 (implementation) completes, before advancing to Gate 1 - - After any refactoring task claims completion - - When code is generated/scaffolded and needs integration verification - -NOT_skip_when: | - - "Code compiles" → Compilation ≠ integration. Dead code compiles. - - "Tests pass" → Unit tests on isolated structs pass without wiring. - - "It's just a struct/interface" → Structs that aren't instantiated are dead code. - - "Wire will happen in next task" → Each task must deliver complete, reachable code. - - "Time pressure" → Unwired code is worse than no code — it creates false confidence. - - "It's a simple task" → Simple tasks still need verification. Partial delivery is not delivery. - -sequence: - after: [ring:dev-implementation] - before: [ring:dev-devops] - -related: - complementary: [ring:dev-cycle, ring:dev-implementation, ring:verification-before-completion, ring:requesting-code-review] - -input_schema: - required: +metadata: + NOT_skip_when: | + - "Code compiles" → Compilation ≠ integration. Dead code compiles. + - "Tests pass" → Unit tests on isolated structs pass without wiring. + - "It's just a struct/interface" → Structs that aren't instantiated are dead code. + - "Wire will happen in next task" → Each task must deliver complete, reachable code. + - "Time pressure" → Unwired code is worse than no code — it creates false confidence. + - "It's a simple task" → Simple tasks still need verification. Partial delivery is not delivery. + input_schema: + required: - name: unit_id type: string - description: "Task or subtask identifier being verified" + description: Task or subtask identifier being verified - name: requirements type: string - description: "Original task requirements or acceptance criteria" + description: Original task requirements or acceptance criteria - name: files_changed type: array items: string - description: "List of files created or modified by Gate 0" - optional: + description: List of files created or modified by Gate 0 + optional: - name: gate0_handoff type: object - description: "Full handoff from Gate 0 implementation" - -output_schema: - format: markdown - required_sections: - - name: "Delivery Verification Summary" - pattern: "^## Delivery Verification Summary" + description: Full handoff from Gate 0 implementation + output_schema: + format: markdown + required_sections: + - name: Delivery Verification Summary + pattern: ^## Delivery Verification Summary required: true - - name: "Requirement Coverage Matrix" - pattern: "^## Requirement Coverage Matrix" + - name: Requirement Coverage Matrix + pattern: ^## Requirement Coverage Matrix required: true - - name: "Integration Verification" - pattern: "^## Integration Verification" + - name: Integration Verification + pattern: ^## Integration Verification required: true - - name: "Dead Code Detection" - pattern: "^## Dead Code Detection" + - name: Dead Code Detection + pattern: ^## Dead Code Detection required: true - - name: "Verdict" - pattern: "^## Verdict" + - name: Verdict + pattern: ^## Verdict required: true - - name: "Return to Gate 0" - pattern: "^## Return to Gate 0" + - name: Return to Gate 0 + pattern: ^## Return to Gate 0 required: true - description: "Mandatory when verdict is PARTIAL or FAIL. Lists specific undelivered requirements with fix instructions for Gate 0." - metrics: + description: Mandatory when verdict is PARTIAL or FAIL. Lists specific undelivered requirements with fix instructions for Gate 0. + metrics: - name: result type: enum - values: [PASS, FAIL, PARTIAL] + values: + - PASS + - FAIL + - PARTIAL - name: requirements_total type: integer - name: requirements_delivered @@ -81,7 +69,23 @@ output_schema: type: integer - name: remediation_items type: integer - description: "Number of fix instructions returned to Gate 0 (0 when PASS)" + description: Number of fix instructions returned to Gate 0 (0 when PASS) + related: + complementary: + - ring:dev-cycle + - ring:dev-implementation + - ring:verification-before-completion + - ring:requesting-code-review + sequence: + after: + - ring:dev-implementation + before: + - ring:dev-devops + trigger: | + - After Gate 0 (implementation) completes, before advancing to Gate 1 + - After any refactoring task claims completion + - When code is generated/scaffolded and needs integration verification + version: 1.0.0 --- # Delivery Verification Gate diff --git a/dev-team/skills/dev-devops/SKILL.md b/dev-team/skills/dev-devops/SKILL.md index a78a4a32..67b97834 100644 --- a/dev-team/skills/dev-devops/SKILL.md +++ b/dev-team/skills/dev-devops/SKILL.md @@ -1,5 +1,5 @@ --- -name: ring:dev-devops +name: dev-devops description: | Gate 1 of the development cycle. Creates/updates Docker configuration, docker-compose setup, and environment variables for local development diff --git a/dev-team/skills/dev-feedback-loop/SKILL.md b/dev-team/skills/dev-feedback-loop/SKILL.md index bc9d09c3..208c6bae 100644 --- a/dev-team/skills/dev-feedback-loop/SKILL.md +++ b/dev-team/skills/dev-feedback-loop/SKILL.md @@ -1,29 +1,28 @@ --- -name: ring:dev-feedback-loop +name: dev-feedback-loop description: | Development cycle feedback system - calculates assertiveness scores, analyzes prompt quality for all agents executed, aggregates cycle metrics, performs root cause analysis on failures, and generates improvement reports to docs/feedbacks/cycle-{date}/. - -trigger: | - - After task completion (any gate outcome) - - After validation approval or rejection - - At end of development cycle - - When assertiveness drops below threshold - -skip_when: | - - Task still in progress -> wait for completion - - Feedback already recorded for this task -> proceed - -NOT_skip_when: | - - "Exploratory/spike work" → all work produces learnings. Track metrics for spikes too. - - "Just experimenting" → Experiments need metrics to measure success. No exceptions. - -sequence: - after: [ring:dev-validation] - -related: - complementary: [ring:dev-cycle, ring:dev-validation] +metadata: + NOT_skip_when: | + - "Exploratory/spike work" → all work produces learnings. Track metrics for spikes too. + - "Just experimenting" → Experiments need metrics to measure success. No exceptions. + related: + complementary: + - ring:dev-cycle + - ring:dev-validation + sequence: + after: + - ring:dev-validation + skip_when: | + - Task still in progress -> wait for completion + - Feedback already recorded for this task -> proceed + trigger: | + - After task completion (any gate outcome) + - After validation approval or rejection + - At end of development cycle + - When assertiveness drops below threshold --- # Dev Feedback Loop diff --git a/dev-team/skills/dev-frontend-accessibility/SKILL.md b/dev-team/skills/dev-frontend-accessibility/SKILL.md index ff9d020d..ddf54b61 100644 --- a/dev-team/skills/dev-frontend-accessibility/SKILL.md +++ b/dev-team/skills/dev-frontend-accessibility/SKILL.md @@ -1,5 +1,5 @@ --- -name: ring:dev-frontend-accessibility +name: dev-frontend-accessibility title: Frontend development cycle accessibility testing (Gate 2) category: development-cycle-frontend tier: 1 diff --git a/dev-team/skills/dev-frontend-e2e/SKILL.md b/dev-team/skills/dev-frontend-e2e/SKILL.md index 9eaf32df..6ed30455 100644 --- a/dev-team/skills/dev-frontend-e2e/SKILL.md +++ b/dev-team/skills/dev-frontend-e2e/SKILL.md @@ -1,5 +1,5 @@ --- -name: ring:dev-frontend-e2e +name: dev-frontend-e2e title: Frontend development cycle E2E testing (Gate 5) category: development-cycle-frontend tier: 1 diff --git a/dev-team/skills/dev-frontend-performance/SKILL.md b/dev-team/skills/dev-frontend-performance/SKILL.md index 090d88f8..0db99259 100644 --- a/dev-team/skills/dev-frontend-performance/SKILL.md +++ b/dev-team/skills/dev-frontend-performance/SKILL.md @@ -1,5 +1,5 @@ --- -name: ring:dev-frontend-performance +name: dev-frontend-performance title: Frontend development cycle performance testing (Gate 6) category: development-cycle-frontend tier: 1 diff --git a/dev-team/skills/dev-frontend-visual/SKILL.md b/dev-team/skills/dev-frontend-visual/SKILL.md index a01e3a28..0b9e5e62 100644 --- a/dev-team/skills/dev-frontend-visual/SKILL.md +++ b/dev-team/skills/dev-frontend-visual/SKILL.md @@ -1,5 +1,5 @@ --- -name: ring:dev-frontend-visual +name: dev-frontend-visual title: Frontend development cycle visual/snapshot testing (Gate 4) category: development-cycle-frontend tier: 1 diff --git a/dev-team/skills/dev-fuzz-testing/SKILL.md b/dev-team/skills/dev-fuzz-testing/SKILL.md index e2cb93a2..70ac7ade 100644 --- a/dev-team/skills/dev-fuzz-testing/SKILL.md +++ b/dev-team/skills/dev-fuzz-testing/SKILL.md @@ -1,5 +1,5 @@ --- -name: ring:dev-fuzz-testing +name: dev-fuzz-testing title: Development cycle fuzz testing (Gate 4) category: development-cycle tier: 1 diff --git a/dev-team/skills/dev-goroutine-leak-testing/SKILL.md b/dev-team/skills/dev-goroutine-leak-testing/SKILL.md index 12573c05..9927774d 100644 --- a/dev-team/skills/dev-goroutine-leak-testing/SKILL.md +++ b/dev-team/skills/dev-goroutine-leak-testing/SKILL.md @@ -1,66 +1,49 @@ --- -name: ring:dev-goroutine-leak-testing -type: testing -author: ring-dev-team -version: 0.1.0 -description: | - Goroutine leak detection skill - detects goroutine usage in Go code, runs goleak - to identify memory leaks, and dispatches ring:backend-engineer-golang to fix leaks - and create regression tests using the goleak framework. - -trigger: | - - Code contains goroutine patterns (go func(), go methodCall()) - - After unit testing gate or during code review - - Suspected memory leak in production - - Need to verify goroutine-heavy code doesn't leak - -NOT_skip_when: | - - "Unit tests cover this" → Unit tests don't detect goroutine leaks. goleak does. - - "Goroutine will exit eventually" → Eventually = memory leak = OOM crash. - - "Process restart cleans it" → Restart = downtime. Prevent leaks instead. - -sequence: - after: [ring:dev-unit-testing] - before: [ring:requesting-code-review] - -related: - complementary: [ring:qa-analyst, ring:backend-engineer-golang] - dispatches: [ring:backend-engineer-golang] - -input_schema: - required: +name: dev-goroutine-leak-testing +description: "Goroutine leak detection skill - detects goroutine usage in Go code, runs goleak \nto identify memory leaks, and dispatches ring:backend-engineer-golang to fix leaks\nand create regression\ + \ tests using the goleak framework.\n" +metadata: + NOT_skip_when: | + - "Unit tests cover this" → Unit tests don't detect goroutine leaks. goleak does. + - "Goroutine will exit eventually" → Eventually = memory leak = OOM crash. + - "Process restart cleans it" → Restart = downtime. Prevent leaks instead. + author: ring-dev-team + input_schema: + required: - name: target_path type: string - description: "Path to Go package or directory to analyze" - optional: + description: Path to Go package or directory to analyze + optional: - name: exclude_patterns type: array items: string - description: "Patterns to exclude from analysis (e.g., vendor/, mocks/)" + description: Patterns to exclude from analysis (e.g., vendor/, mocks/) - name: known_safe_goroutines type: array items: string - description: "Function signatures known to be safe (external libs)" - -output_schema: - format: markdown - required_sections: - - name: "Goroutine Detection Summary" - pattern: "^## Goroutine Detection Summary" + description: Function signatures known to be safe (external libs) + output_schema: + format: markdown + required_sections: + - name: Goroutine Detection Summary + pattern: ^## Goroutine Detection Summary required: true - - name: "goleak Coverage" - pattern: "^## goleak Coverage" + - name: goleak Coverage + pattern: ^## goleak Coverage required: true - - name: "Leak Findings" - pattern: "^## Leak Findings" + - name: Leak Findings + pattern: ^## Leak Findings required: true - - name: "Required Actions" - pattern: "^## Required Actions" + - name: Required Actions + pattern: ^## Required Actions required: true - metrics: + metrics: - name: result type: enum - values: [PASS, FAIL, NEEDS_ACTION] + values: + - PASS + - FAIL + - NEEDS_ACTION - name: goroutine_files type: integer - name: packages_with_goleak @@ -69,6 +52,24 @@ output_schema: type: integer - name: leaks_detected type: integer + related: + complementary: + - ring:qa-analyst + - ring:backend-engineer-golang + dispatches: + - ring:backend-engineer-golang + sequence: + after: + - ring:dev-unit-testing + before: + - ring:requesting-code-review + trigger: | + - Code contains goroutine patterns (go func(), go methodCall()) + - After unit testing gate or during code review + - Suspected memory leak in production + - Need to verify goroutine-heavy code doesn't leak + type: testing + version: 0.1.0 --- # Goroutine Leak Testing Skill diff --git a/dev-team/skills/dev-helm/SKILL.md b/dev-team/skills/dev-helm/SKILL.md index c5f7f759..4047a08a 100644 --- a/dev-team/skills/dev-helm/SKILL.md +++ b/dev-team/skills/dev-helm/SKILL.md @@ -1,91 +1,96 @@ --- -name: ring:dev-helm +name: dev-helm description: | Mandatory skill for creating and maintaining Helm charts following Lerian conventions. Enforces standardized chart structure, values organization, template patterns, security defaults, and dependency management. - -trigger: | - - Creating a new Helm chart for any Lerian service - - Modifying an existing Helm chart (adding components, dependencies, templates) - - Reviewing a Helm chart PR for convention compliance - - Migrating a docker-compose setup to Helm - -NOT_skip_when: | - - "It's a simple chart, I don't need all that" → Every chart grows. Structure prevents debt. - - "I'll add security later" → Security is foundational, not an afterthought. - - "The defaults are fine" → Lerian has specific conventions that MUST be followed. - - "I'll just copy another chart" → Copying without understanding introduces drift. Use this skill. - -skip_when: | - - Modifying only application code (no chart changes) - - Working on non-Helm deployment (docker-compose only) → Use ring:dev-devops - -sequence: - after: [ring:dev-devops] - before: [ring:dev-sre] - -dependencies: [ring:dev-devops] -role: orchestrator - -related: - complementary: [ring:dev-devops, ring:dev-sre, ring:dev-implementation] - similar: [ring:dev-devops] - -input_schema: - required: +metadata: + NOT_skip_when: | + - "It's a simple chart, I don't need all that" → Every chart grows. Structure prevents debt. + - "I'll add security later" → Security is foundational, not an afterthought. + - "The defaults are fine" → Lerian has specific conventions that MUST be followed. + - "I'll just copy another chart" → Copying without understanding introduces drift. Use this skill. + dependencies: + - ring:dev-devops + input_schema: + required: - name: service_name type: string - description: "Name of the service (e.g., reporter, tracer, plugin-fees)" + description: Name of the service (e.g., reporter, tracer, plugin-fees) - name: chart_type type: string - enum: [single, multi-component, umbrella] - description: "Chart architecture type" + enum: + - single + - multi-component + - umbrella + description: Chart architecture type - name: components type: array items: string - description: "List of components (e.g., [manager, worker] or [pix, inbound, outbound])" - optional: + description: List of components (e.g., [manager, worker] or [pix, inbound, outbound]) + optional: - name: dependencies type: array items: string - description: "Infrastructure dependencies (postgresql, mongodb, rabbitmq, valkey, keda)" + description: Infrastructure dependencies (postgresql, mongodb, rabbitmq, valkey, keda) - name: has_worker type: boolean - description: "Whether the service has a background worker (ScaledJob/Deployment)" + description: Whether the service has a background worker (ScaledJob/Deployment) default: false - name: namespace type: string - description: "Target Kubernetes namespace" - -output_schema: - format: markdown - required_sections: - - name: "Chart Structure" - pattern: "^## Chart Structure" + description: Target Kubernetes namespace + output_schema: + format: markdown + required_sections: + - name: Chart Structure + pattern: ^## Chart Structure required: true - - name: "Validation Results" - pattern: "^## Validation Results" + - name: Validation Results + pattern: ^## Validation Results required: true - metrics: + metrics: - name: compliance_status type: enum - values: [PASS, FAIL, PARTIAL] + values: + - PASS + - FAIL + - PARTIAL - name: files_created type: integer - -verification: - automated: - - command: "helm lint ." - description: "Helm linter passes" - success_pattern: "0 chart\\(s\\) failed" - - command: "helm template test . 2>&1 | head -5" - description: "Template renders without errors" - success_pattern: '^(apiVersion|-{3})' - manual: - - "All values.yaml fields follow Lerian naming conventions" - - "Secrets do not contain real credentials" - - "Health check paths match application endpoints" + related: + complementary: + - ring:dev-devops + - ring:dev-sre + - ring:dev-implementation + similar: + - ring:dev-devops + role: orchestrator + sequence: + after: + - ring:dev-devops + before: + - ring:dev-sre + skip_when: | + - Modifying only application code (no chart changes) + - Working on non-Helm deployment (docker-compose only) → Use ring:dev-devops + trigger: | + - Creating a new Helm chart for any Lerian service + - Modifying an existing Helm chart (adding components, dependencies, templates) + - Reviewing a Helm chart PR for convention compliance + - Migrating a docker-compose setup to Helm + verification: + automated: + - command: helm lint . + description: Helm linter passes + success_pattern: 0 chart\(s\) failed + - command: helm template test . 2>&1 | head -5 + description: Template renders without errors + success_pattern: ^(apiVersion|-{3}) + manual: + - All values.yaml fields follow Lerian naming conventions + - Secrets do not contain real credentials + - Health check paths match application endpoints --- # Helm Chart Creation & Maintenance (Lerian Conventions) diff --git a/dev-team/skills/dev-implementation/SKILL.md b/dev-team/skills/dev-implementation/SKILL.md index 7221819a..af823233 100644 --- a/dev-team/skills/dev-implementation/SKILL.md +++ b/dev-team/skills/dev-implementation/SKILL.md @@ -1,5 +1,5 @@ --- -name: ring:dev-implementation +name: dev-implementation description: | Gate 0 of the development cycle. Executes code implementation using the appropriate specialized agent based on task content and project language. Handles TDD workflow diff --git a/dev-team/skills/dev-integration-testing/SKILL.md b/dev-team/skills/dev-integration-testing/SKILL.md index b5774c01..32310eea 100644 --- a/dev-team/skills/dev-integration-testing/SKILL.md +++ b/dev-team/skills/dev-integration-testing/SKILL.md @@ -1,5 +1,5 @@ --- -name: ring:dev-integration-testing +name: dev-integration-testing title: Development cycle integration testing (Gate 6) category: development-cycle tier: 1 diff --git a/dev-team/skills/dev-migrate-v4/SKILL.md b/dev-team/skills/dev-migrate-v4/SKILL.md index e8c026eb..31d691b1 100644 --- a/dev-team/skills/dev-migrate-v4/SKILL.md +++ b/dev-team/skills/dev-migrate-v4/SKILL.md @@ -1,53 +1,54 @@ --- -name: ring:dev-migrate-v4 +name: dev-migrate-v4 description: | Analyzes a Go service using lib-commons v2/v3 and generates a visual migration report showing every change needed to upgrade to lib-commons v4. Produces an interactive HTML page (via ring:visual-explainer) and optionally generates refactoring tasks for ring:dev-cycle. -trigger: | - - User wants to migrate a Go service from lib-commons v2 or v3 to v4 - - User asks about lib-commons version upgrade - - User wants to see what needs to change for v4 - - User runs /ring:migrate-v4 - -skip_when: | - - Project already uses lib-commons/v4 → Report compliance status only - - Project is not Go → Not applicable - - Project does not use lib-commons → Not applicable - -prerequisite: | - - Go project with go.mod containing lib-commons/v2 or lib-commons/v3 - - docs/PROJECT_RULES.md exists (recommended but not blocking) - -sequence: - after: [ring:dev-cycle] - -related: - complementary: [ring:dev-cycle, ring:dev-refactor, ring:codebase-explorer, ring:visual-explainer, ring:backend-engineer-golang] - -verification: - automated: - - command: "grep 'lib-commons/v4' go.mod" - description: "go.mod declares lib-commons v4" - success_pattern: "v4" - - command: "grep -rn 'lib-commons/v2\\|lib-commons/v3' --include='*.go' . | grep -v indirect | wc -l" - description: "Zero v2/v3 direct imports remain" - success_pattern: "^0$" - -examples: - - name: "Analyze and show visual report" - invocation: "/ring:migrate-v4" - expected_flow: "Scan → Map → Visual HTML report opened in browser" - - name: "Generate tasks for dev-cycle" - invocation: "/ring:migrate-v4 --tasks" - expected_flow: "Scan → Map → Visual report → migration-v4-tasks.md saved" - - name: "Full automatic migration" - invocation: "/ring:migrate-v4 --execute" - expected_flow: "Scan → Map → Visual report → tasks.md → ring:dev-cycle dispatched through all 10 gates" - - name: "Specific repository path" - invocation: "/ring:migrate-v4 /path/to/service --execute" - expected_flow: "Same as above but targets specific path" +metadata: + examples: + - name: Analyze and show visual report + invocation: /ring:migrate-v4 + expected_flow: Scan → Map → Visual HTML report opened in browser + - name: Generate tasks for dev-cycle + invocation: /ring:migrate-v4 --tasks + expected_flow: Scan → Map → Visual report → migration-v4-tasks.md saved + - name: Full automatic migration + invocation: /ring:migrate-v4 --execute + expected_flow: Scan → Map → Visual report → tasks.md → ring:dev-cycle dispatched through all 10 gates + - name: Specific repository path + invocation: /ring:migrate-v4 /path/to/service --execute + expected_flow: Same as above but targets specific path + prerequisite: | + - Go project with go.mod containing lib-commons/v2 or lib-commons/v3 + - docs/PROJECT_RULES.md exists (recommended but not blocking) + related: + complementary: + - ring:dev-cycle + - ring:dev-refactor + - ring:codebase-explorer + - ring:visual-explainer + - ring:backend-engineer-golang + sequence: + after: + - ring:dev-cycle + skip_when: | + - Project already uses lib-commons/v4 → Report compliance status only + - Project is not Go → Not applicable + - Project does not use lib-commons → Not applicable + trigger: | + - User wants to migrate a Go service from lib-commons v2 or v3 to v4 + - User asks about lib-commons version upgrade + - User wants to see what needs to change for v4 + - User runs /ring:migrate-v4 + verification: + automated: + - command: grep 'lib-commons/v4' go.mod + description: go.mod declares lib-commons v4 + success_pattern: v4 + - command: grep -rn 'lib-commons/v2\|lib-commons/v3' --include='*.go' . | grep -v indirect | wc -l + description: Zero v2/v3 direct imports remain + success_pattern: ^0$ --- # Dev Migrate v4 diff --git a/dev-team/skills/dev-multi-tenant/SKILL.md b/dev-team/skills/dev-multi-tenant/SKILL.md index 61f5f6d9..ea270338 100644 --- a/dev-team/skills/dev-multi-tenant/SKILL.md +++ b/dev-team/skills/dev-multi-tenant/SKILL.md @@ -1,8 +1,5 @@ --- -name: ring:dev-multi-tenant -slug: dev-multi-tenant -version: 2.0.0 -type: skill +name: dev-multi-tenant description: | Multi-tenant development cycle orchestrator following Ring Standards. Auto-detects the service stack (PostgreSQL, MongoDB, Redis, RabbitMQ, S3) @@ -14,51 +11,53 @@ description: | MUST update lib-commons v3 first; lib-auth v2 depends on it. Both are required dependencies. Each gate dispatches ring:backend-engineer-golang with context and section references. The agent loads multi-tenant.md via WebFetch and has all code examples. - -trigger: | - - User requests multi-tenant implementation for a Go service - - User asks to add tenant isolation to an existing service - - Task mentions "multi-tenant", "tenant isolation", "tenant-manager", "postgres.Manager", "MultiPoolMiddleware" - -prerequisite: | - - Go service with existing single-tenant functionality - -NOT_skip_when: | - - "organization_id already exists" → organization_id is NOT multi-tenant. tenantId via JWT is required. - - "Just need to connect the wiring" → Multi-tenant requires lib-commons v3 tenant-manager sub-packages. - - "lib-commons v3 upgrade is too risky" → REQUIRES lib-commons v3 tenant-manager sub-packages. No v3 = no multi-tenant. - - "Service already has multi-tenant" → Existence ≠ compliance. MUST replace non-standard implementations with Ring canonical model. - - "Multi-tenant is already done" → Every gate verifies compliance. MUST fix non-compliant code — it is wrong, not done. - -sequence: - after: [ring:dev-devops] - -related: - complementary: [ring:dev-cycle, ring:dev-implementation, ring:dev-devops, ring:dev-unit-testing, ring:requesting-code-review, ring:dev-validation] - -input_schema: - description: | - When invoked from ring:dev-cycle (post-cycle step), receives structured handoff context. - When invoked standalone (direct user request), these fields are auto-detected in Gate 0. - fields: +metadata: + NOT_skip_when: | + - "organization_id already exists" → organization_id is NOT multi-tenant. tenantId via JWT is required. + - "Just need to connect the wiring" → Multi-tenant requires lib-commons v3 tenant-manager sub-packages. + - "lib-commons v3 upgrade is too risky" → REQUIRES lib-commons v3 tenant-manager sub-packages. No v3 = no multi-tenant. + - "Service already has multi-tenant" → Existence ≠ compliance. MUST replace non-standard implementations with Ring canonical model. + - "Multi-tenant is already done" → Every gate verifies compliance. MUST fix non-compliant code — it is wrong, not done. + examples: + - name: Add multi-tenant to a service + invocation: /ring:dev-multi-tenant + expected_flow: |- + 1. Gate 0: Auto-detect stack + service type (plugin vs product) + 2. Gate 1: Analyze codebase (build implementation roadmap) + 3. Gate 1.5: Visual implementation preview (HTML report for developer approval) + 4. Gates 2-5: Implementation (agent loads multi-tenant.md, follows roadmap) + 5. Gate 5.5: M2M Secret Manager for plugin auth (if plugin) + 6. Gate 6: RabbitMQ multi-tenant (if RabbitMQ detected) + 7. Gate 7: Metrics & Backward compatibility + 8. Gate 8: Tests + 9. Gate 9: Code review + 10. Gate 10: User validation + 11. Gate 11: Activation guide + input_schema: + description: | + When invoked from ring:dev-cycle (post-cycle step), receives structured handoff context. + When invoked standalone (direct user request), these fields are auto-detected in Gate 0. + fields: - name: execution_mode type: string - enum: ["FULL", "SCOPED"] - description: "FULL = complete 12-gate cycle. SCOPED = only adapt new files (when existing MT is compliant)." + enum: + - FULL + - SCOPED + description: FULL = complete 12-gate cycle. SCOPED = only adapt new files (when existing MT is compliant). required: false - default: "FULL" + default: FULL - name: files_changed type: array items: string - description: "File paths changed during dev-cycle (only in SCOPED mode). Used to limit Gate 5 scope." + description: File paths changed during dev-cycle (only in SCOPED mode). Used to limit Gate 5 scope. required: false - name: multi_tenant_exists type: boolean - description: "Whether multi-tenant code was detected by dev-cycle Step 1.5." + description: Whether multi-tenant code was detected by dev-cycle Step 1.5. required: false - name: multi_tenant_compliant type: boolean - description: "Whether existing MT code passed compliance audit in dev-cycle Step 1.5." + description: Whether existing MT code passed compliance audit in dev-cycle Step 1.5. required: false - name: detected_dependencies type: object @@ -68,52 +67,55 @@ input_schema: redis: boolean rabbitmq: boolean s3: boolean - description: "Stack detection from dev-cycle. Each key indicates whether that technology was detected." + description: Stack detection from dev-cycle. Each key indicates whether that technology was detected. required: false - name: skip_gates type: array items: string - description: "Gate identifiers to skip (e.g., '0', '1.5', '5.5'). Set by dev-cycle based on execution_mode." + description: Gate identifiers to skip (e.g., '0', '1.5', '5.5'). Set by dev-cycle based on execution_mode. required: false - -output_schema: - format: markdown - required_sections: - - name: "Multi-Tenant Cycle Summary" - pattern: "^## Multi-Tenant Cycle Summary" + output_schema: + format: markdown + required_sections: + - name: Multi-Tenant Cycle Summary + pattern: ^## Multi-Tenant Cycle Summary required: true - - name: "Stack Detection" - pattern: "^## Stack Detection" + - name: Stack Detection + pattern: ^## Stack Detection required: true - - name: "Gate Results" - pattern: "^## Gate Results" + - name: Gate Results + pattern: ^## Gate Results required: true - - name: "Verification" - pattern: "^## Verification" + - name: Verification + pattern: ^## Verification required: true - metrics: + metrics: - name: gates_passed type: integer - name: gates_failed type: integer - name: total_files_changed type: integer - -examples: - - name: "Add multi-tenant to a service" - invocation: "/ring:dev-multi-tenant" - expected_flow: | - 1. Gate 0: Auto-detect stack + service type (plugin vs product) - 2. Gate 1: Analyze codebase (build implementation roadmap) - 3. Gate 1.5: Visual implementation preview (HTML report for developer approval) - 4. Gates 2-5: Implementation (agent loads multi-tenant.md, follows roadmap) - 5. Gate 5.5: M2M Secret Manager for plugin auth (if plugin) - 6. Gate 6: RabbitMQ multi-tenant (if RabbitMQ detected) - 7. Gate 7: Metrics & Backward compatibility - 8. Gate 8: Tests - 9. Gate 9: Code review - 10. Gate 10: User validation - 11. Gate 11: Activation guide + prerequisite: | + - Go service with existing single-tenant functionality + related: + complementary: + - ring:dev-cycle + - ring:dev-implementation + - ring:dev-devops + - ring:dev-unit-testing + - ring:requesting-code-review + - ring:dev-validation + sequence: + after: + - ring:dev-devops + slug: dev-multi-tenant + trigger: | + - User requests multi-tenant implementation for a Go service + - User asks to add tenant isolation to an existing service + - Task mentions "multi-tenant", "tenant isolation", "tenant-manager", "postgres.Manager", "MultiPoolMiddleware" + type: skill + version: 2.0.0 --- # Multi-Tenant Development Cycle diff --git a/dev-team/skills/dev-property-testing/SKILL.md b/dev-team/skills/dev-property-testing/SKILL.md index 455c5310..45f77a87 100644 --- a/dev-team/skills/dev-property-testing/SKILL.md +++ b/dev-team/skills/dev-property-testing/SKILL.md @@ -1,5 +1,5 @@ --- -name: ring:dev-property-testing +name: dev-property-testing title: Development cycle property-based testing (Gate 5) category: development-cycle tier: 1 diff --git a/dev-team/skills/dev-refactor-frontend/SKILL.md b/dev-team/skills/dev-refactor-frontend/SKILL.md index 503bd16c..8a4558f1 100644 --- a/dev-team/skills/dev-refactor-frontend/SKILL.md +++ b/dev-team/skills/dev-refactor-frontend/SKILL.md @@ -1,61 +1,60 @@ --- -name: ring:dev-refactor-frontend +name: dev-refactor-frontend description: | Analyzes frontend codebase against Ring standards and generates refactoring tasks for ring:dev-cycle-frontend. Dispatches frontend-specific agents in ANALYSIS mode. - -trigger: | - - User wants to refactor existing frontend project to follow standards - - Legacy React/Next.js codebase needs modernization - - Frontend project audit requested - -skip_when: | - - Greenfield project -> Use /ring:pre-dev-* instead - - Single file fix -> Use ring:dev-cycle-frontend directly - - Backend-only project -> Use ring:dev-refactor instead - -sequence: - before: [ring:dev-cycle-frontend] - -related: - complementary: [ring:dev-refactor, ring:dev-cycle-frontend, ring:using-dev-team] - -input_schema: - required: [] - optional: +metadata: + input_schema: + required: [] + optional: - name: project_path type: string - description: "Path to frontend project root (default: current directory)" + description: 'Path to frontend project root (default: current directory)' - name: prompt type: string - description: "Direct instruction for refactoring focus" + description: Direct instruction for refactoring focus - name: standards_path type: string - description: "Custom standards file path (default: Ring standards via WebFetch)" + description: 'Custom standards file path (default: Ring standards via WebFetch)' - name: analyze_only type: boolean - description: "Generate report without executing ring:dev-cycle-frontend" + description: Generate report without executing ring:dev-cycle-frontend - name: critical_only type: boolean - description: "Limit execution to Critical and High severity (analysis still tracks all)" + description: Limit execution to Critical and High severity (analysis still tracks all) - name: dry_run type: boolean - description: "Show what would be analyzed without executing" - -output_schema: - format: markdown - artifacts: - - name: "codebase-report.md" - description: "Codebase analysis from ring:codebase-explorer" - - name: "reports/{agent-name}-report.md" - description: "Individual agent analysis reports" - - name: "findings.md" - description: "All findings mapped from agent reports" - - name: "tasks.md" - description: "1:1 mapped REFACTOR-XXX tasks from findings" - - name: "change-report.html" - description: "Visual HTML change report from ring:visual-explainer" - traceability: "Ring Standard -> Agent Report -> FINDING-XXX -> REFACTOR-XXX -> Implementation" + description: Show what would be analyzed without executing + output_schema: + format: markdown + artifacts: + - name: codebase-report.md + description: Codebase analysis from ring:codebase-explorer + - name: reports/{agent-name}-report.md + description: Individual agent analysis reports + - name: findings.md + description: All findings mapped from agent reports + - name: tasks.md + description: 1:1 mapped REFACTOR-XXX tasks from findings + - name: change-report.html + description: Visual HTML change report from ring:visual-explainer + traceability: Ring Standard -> Agent Report -> FINDING-XXX -> REFACTOR-XXX -> Implementation + related: + complementary: + - ring:dev-refactor + - ring:dev-cycle-frontend + - ring:using-dev-team + sequence: + before: + - ring:dev-cycle-frontend + skip_when: | + - Greenfield project -> Use /ring:pre-dev-* instead + - Single file fix -> Use ring:dev-cycle-frontend directly + - Backend-only project -> Use ring:dev-refactor instead + trigger: | + - User wants to refactor existing frontend project to follow standards + - Legacy React/Next.js codebase needs modernization + - Frontend project audit requested --- # Dev Refactor Frontend Skill diff --git a/dev-team/skills/dev-refactor/SKILL.md b/dev-team/skills/dev-refactor/SKILL.md index 9785971e..416b1040 100644 --- a/dev-team/skills/dev-refactor/SKILL.md +++ b/dev-team/skills/dev-refactor/SKILL.md @@ -1,14 +1,14 @@ --- -name: ring:dev-refactor +name: dev-refactor description: Analyzes backend codebase (Go/TypeScript) against standards and generates refactoring tasks for ring:dev-cycle. For frontend projects, use ring:dev-refactor-frontend instead. -trigger: | - - User wants to refactor existing project to follow standards - - Legacy codebase needs modernization - - Project audit requested - -skip_when: | - - Greenfield project → Use /pre-dev-* instead - - Single file fix → Use ring:dev-cycle directly +metadata: + skip_when: |- + - Greenfield project → Use /pre-dev-* instead + - Single file fix → Use ring:dev-cycle directly + trigger: | + - User wants to refactor existing project to follow standards + - Legacy codebase needs modernization + - Project audit requested --- # Dev Refactor Skill diff --git a/dev-team/skills/dev-service-discovery/SKILL.md b/dev-team/skills/dev-service-discovery/SKILL.md index f18a898c..ec724fba 100644 --- a/dev-team/skills/dev-service-discovery/SKILL.md +++ b/dev-team/skills/dev-service-discovery/SKILL.md @@ -1,8 +1,5 @@ --- -name: ring:dev-service-discovery -slug: dev-service-discovery -version: 1.2.0 -type: skill +name: dev-service-discovery description: | Scans the current Go project and identifies the Service → Module → Resource hierarchy for tenant-manager registration. Detects service name and type, @@ -17,35 +14,14 @@ description: | Also detects database names per module, cross-references them across modules to find shared databases, and flags them for single-provision in tenant-manager. - -trigger: | - - User wants to know what to provision in tenant-manager for a service - - User asks "what services/modules/resources does this project have?" - - User needs to register a service in the tenant-manager catalog - - Before running ring:dev-multi-tenant on a new service - - User asks about MongoDB indexes in a project - -prerequisite: | - - Go project with go.mod in the current working directory - -NOT_skip_when: | - - "Service is simple, I can see the structure" → Detection must be evidence-based, not assumed. - - "Already know the modules" → Knowledge ≠ verified. Run the scan. - -related: - complementary: [ring:dev-multi-tenant, ring:dev-devops, ring:exploring-codebase] - -output_schema: - format: html - required_sections: - - name: "Service Discovery Report" - pattern: "^## Service Discovery Report" - required: true - -examples: - - name: "Scan current project" - invocation: "/ring:dev-service-discovery" - expected_flow: | +metadata: + NOT_skip_when: | + - "Service is simple, I can see the structure" → Detection must be evidence-based, not assumed. + - "Already know the modules" → Knowledge ≠ verified. Run the scan. + examples: + - name: Scan current project + invocation: /ring:dev-service-discovery + expected_flow: |- 1. Detect service identity (ApplicationName, type) 2. Detect modules (WithModule calls, component structure) 3. Detect resources per module (PostgreSQL, MongoDB, RabbitMQ) @@ -54,6 +30,28 @@ examples: 6. Detect MongoDB indexes (in-code + scripts) 7. Generate visual HTML report with shared database warnings 8. Open in browser for review + output_schema: + format: html + required_sections: + - name: Service Discovery Report + pattern: ^## Service Discovery Report + required: true + prerequisite: | + - Go project with go.mod in the current working directory + related: + complementary: + - ring:dev-multi-tenant + - ring:dev-devops + - ring:exploring-codebase + slug: dev-service-discovery + trigger: | + - User wants to know what to provision in tenant-manager for a service + - User asks "what services/modules/resources does this project have?" + - User needs to register a service in the tenant-manager catalog + - Before running ring:dev-multi-tenant on a new service + - User asks about MongoDB indexes in a project + type: skill + version: 1.2.0 --- # Service Discovery for Tenant-Manager diff --git a/dev-team/skills/dev-sre/SKILL.md b/dev-team/skills/dev-sre/SKILL.md index 35bc4162..4d59211a 100644 --- a/dev-team/skills/dev-sre/SKILL.md +++ b/dev-team/skills/dev-sre/SKILL.md @@ -1,5 +1,5 @@ --- -name: ring:dev-sre +name: dev-sre description: | Gate 2 of the development cycle. VALIDATES that observability was correctly implemented by developers. Does not implement observability code - only validates it. diff --git a/dev-team/skills/dev-unit-testing/SKILL.md b/dev-team/skills/dev-unit-testing/SKILL.md index 578f0345..294bc47d 100644 --- a/dev-team/skills/dev-unit-testing/SKILL.md +++ b/dev-team/skills/dev-unit-testing/SKILL.md @@ -1,5 +1,5 @@ --- -name: ring:dev-unit-testing +name: dev-unit-testing description: | Gate 3 of development cycle - ensures unit test coverage meets threshold (85%+) for all acceptance criteria using TDD methodology. diff --git a/dev-team/skills/dev-validation/SKILL.md b/dev-team/skills/dev-validation/SKILL.md index 2068c9d0..2601e01f 100644 --- a/dev-team/skills/dev-validation/SKILL.md +++ b/dev-team/skills/dev-validation/SKILL.md @@ -1,54 +1,51 @@ --- -name: ring:dev-validation +name: dev-validation description: | Development cycle validation gate (Gate 5) - validates all acceptance criteria are met and requires explicit user approval before completion. - -trigger: | - - After review gate passes (Gate 4) - - Implementation and tests complete - - Need user sign-off on acceptance criteria - -NOT_skip_when: | - - "Already validated" → Each iteration needs fresh validation. - - "User will validate manually" → Gate 5 IS user validation. Cannot skip. - -sequence: - after: [ring:requesting-code-review] - -related: - complementary: [verification-before-completion] - -verification: - automated: - - command: "go test ./... 2>&1 | grep -c PASS" - description: "All tests pass" - success_pattern: "[1-9][0-9]*" - - command: "cat docs/ring:dev-cycle/current-cycle.json 2>/dev/null || cat docs/ring:dev-refactor/current-cycle.json | jq '.gates[4].verdict'" - description: "Review gate passed" - success_pattern: "PASS" - manual: - - "User has provided explicit APPROVED or REJECTED decision" - - "All acceptance criteria have verified evidence" - - "Validation checklist presented to user" - -examples: - - name: "Successful validation" - context: "4 acceptance criteria, all tests pass" +metadata: + NOT_skip_when: | + - "Already validated" → Each iteration needs fresh validation. + - "User will validate manually" → Gate 5 IS user validation. Cannot skip. + examples: + - name: Successful validation + context: 4 acceptance criteria, all tests pass expected_flow: | 1. Gather evidence for each criterion 2. Build validation checklist with evidence types 3. Present to user with APPROVED/REJECTED options 4. User selects APPROVED 5. Document approval, proceed to feedback loop - - name: "Validation rejection" - context: "AC-3 not met (response time too slow)" - expected_flow: | + - name: Validation rejection + context: AC-3 not met (response time too slow) + expected_flow: |- 1. Present validation checklist 2. User identifies AC-3 failure 3. User selects REJECTED with reason 4. Create remediation task 5. Return to Gate 0 for fixes + related: + complementary: + - verification-before-completion + sequence: + after: + - ring:requesting-code-review + trigger: | + - After review gate passes (Gate 4) + - Implementation and tests complete + - Need user sign-off on acceptance criteria + verification: + automated: + - command: go test ./... 2>&1 | grep -c PASS + description: All tests pass + success_pattern: '[1-9][0-9]*' + - command: cat docs/ring:dev-cycle/current-cycle.json 2>/dev/null || cat docs/ring:dev-refactor/current-cycle.json | jq '.gates[4].verdict' + description: Review gate passed + success_pattern: PASS + manual: + - User has provided explicit APPROVED or REJECTED decision + - All acceptance criteria have verified evidence + - Validation checklist presented to user --- # Dev Validation (Gate 5) diff --git a/dev-team/skills/using-dev-team/SKILL.md b/dev-team/skills/using-dev-team/SKILL.md index 150dcb92..88cb144b 100644 --- a/dev-team/skills/using-dev-team/SKILL.md +++ b/dev-team/skills/using-dev-team/SKILL.md @@ -1,25 +1,24 @@ --- -name: ring:using-dev-team +name: using-dev-team description: | 9 specialist developer agents for backend (Go/TypeScript), DevOps, frontend, design, UI implementation, QA (backend + frontend), and SRE. Dispatch when you need deep technology expertise. - -trigger: | - - Need deep expertise for specific technology (Go, TypeScript) - - Building infrastructure/CI-CD → ring:devops-engineer - - Frontend with design focus → ring:frontend-designer - - Frontend from product-designer specs → ring:ui-engineer - - Backend test strategy → ring:qa-analyst - - Frontend test strategy → ring:qa-analyst-frontend - - Reliability/monitoring → ring:sre - -skip_when: | - - General code review → use default plugin reviewers - - Planning/design → use brainstorming - - Debugging → use ring:systematic-debugging - -related: - similar: [ring:using-ring] +metadata: + related: + similar: + - ring:using-ring + skip_when: | + - General code review → use default plugin reviewers + - Planning/design → use brainstorming + - Debugging → use ring:systematic-debugging + trigger: | + - Need deep expertise for specific technology (Go, TypeScript) + - Building infrastructure/CI-CD → ring:devops-engineer + - Frontend with design focus → ring:frontend-designer + - Frontend from product-designer specs → ring:ui-engineer + - Backend test strategy → ring:qa-analyst + - Frontend test strategy → ring:qa-analyst-frontend + - Reliability/monitoring → ring:sre --- # Using Ring Developer Specialists diff --git a/finops-team/skills/infrastructure-cost-estimation/SKILL.md b/finops-team/skills/infrastructure-cost-estimation/SKILL.md index 8c93485b..2624b509 100644 --- a/finops-team/skills/infrastructure-cost-estimation/SKILL.md +++ b/finops-team/skills/infrastructure-cost-estimation/SKILL.md @@ -1,22 +1,21 @@ --- -name: ring:infrastructure-cost-estimation -version: 6.0.0 +name: infrastructure-cost-estimation description: | Orchestrates infrastructure cost estimation with tier-based or custom TPS sizing. Offers pre-configured tiers (Starter/Growth/Business/Enterprise) or custom TPS input. Skill discovers components, asks shared/dedicated for EACH, selects environment(s), reads actual Helm chart configs, then dispatches agent for accurate calculations. - -trigger: | - - "How much will this cost on AWS?" - - "Estimate infrastructure for [repo]" - - "What should we charge the customer?" - - "Is this deal profitable?" - - Adding new customer to platform - -skip_when: | - - No docker-compose in repo → manual estimation needed - - Non-AWS target → adapt pricing +metadata: + skip_when: |- + - No docker-compose in repo → manual estimation needed + - Non-AWS target → adapt pricing + trigger: | + - "How much will this cost on AWS?" + - "Estimate infrastructure for [repo]" + - "What should we charge the customer?" + - "Is this deal profitable?" + - Adding new customer to platform + version: 6.0.0 --- # Infrastructure Cost Estimation diff --git a/finops-team/skills/regulatory-templates-gate1/SKILL.md b/finops-team/skills/regulatory-templates-gate1/SKILL.md index dfce6d3b..80cba3bc 100644 --- a/finops-team/skills/regulatory-templates-gate1/SKILL.md +++ b/finops-team/skills/regulatory-templates-gate1/SKILL.md @@ -1,26 +1,24 @@ --- -name: ring:regulatory-templates-gate1 +name: regulatory-templates-gate1 description: | Gate 1 sub-skill - performs regulatory compliance analysis, field mapping, batch approval by confidence level, and auto-saves dictionary after approval. Supports both pre-defined templates (dictionary exists) and new templates (any spec). - -dependencies: +metadata: + dependencies: - ring:finops-analyzer - -role: regulatory-analyst - -trigger: | - - regulatory-templates-setup completed - - Need to analyze regulatory specification and map fields - -skip_when: | - - Setup not complete → run setup first - - Gate 1 already passed → proceed to Gate 2 - -sequence: - after: [regulatory-templates-setup] - before: [regulatory-templates-gate2] + role: regulatory-analyst + sequence: + after: + - regulatory-templates-setup + before: + - regulatory-templates-gate2 + skip_when: | + - Setup not complete → run setup first + - Gate 1 already passed → proceed to Gate 2 + trigger: | + - regulatory-templates-setup completed + - Need to analyze regulatory specification and map fields --- # Regulatory Templates - Gate 1: Placeholder Mapping (Post Gate 0) diff --git a/finops-team/skills/regulatory-templates-gate2/SKILL.md b/finops-team/skills/regulatory-templates-gate2/SKILL.md index 95793efa..63494eeb 100644 --- a/finops-team/skills/regulatory-templates-gate2/SKILL.md +++ b/finops-team/skills/regulatory-templates-gate2/SKILL.md @@ -1,20 +1,20 @@ --- -name: ring:regulatory-templates-gate2 +name: regulatory-templates-gate2 description: | Gate 2 sub-skill - validates uncertain mappings from Gate 1 and confirms all field specifications through testing. - -trigger: | - - Gate 1 PASSED - - Need to validate mappings before template generation - -skip_when: | - - Gate 1 not passed → complete Gate 1 first - - Gate 2 already passed → proceed to Gate 3 - -sequence: - after: [regulatory-templates-gate1] - before: [regulatory-templates-gate3] +metadata: + sequence: + after: + - regulatory-templates-gate1 + before: + - regulatory-templates-gate3 + skip_when: | + - Gate 1 not passed → complete Gate 1 first + - Gate 2 already passed → proceed to Gate 3 + trigger: | + - Gate 1 PASSED + - Need to validate mappings before template generation --- # Regulatory Templates - Gate 2: Technical Validation diff --git a/finops-team/skills/regulatory-templates-gate3/SKILL.md b/finops-team/skills/regulatory-templates-gate3/SKILL.md index 4be335a7..419791b4 100644 --- a/finops-team/skills/regulatory-templates-gate3/SKILL.md +++ b/finops-team/skills/regulatory-templates-gate3/SKILL.md @@ -1,19 +1,18 @@ --- -name: ring:regulatory-templates-gate3 +name: regulatory-templates-gate3 description: | Gate 3 sub-skill - generates complete .tpl template file with all validated mappings from Gates 1-2. - -trigger: | - - Gate 2 PASSED - - Ready to generate production template file - -skip_when: | - - Gate 2 not passed → complete Gate 2 first - - Template already generated → verify or regenerate - -sequence: - after: [regulatory-templates-gate2] +metadata: + sequence: + after: + - regulatory-templates-gate2 + skip_when: | + - Gate 2 not passed → complete Gate 2 first + - Template already generated → verify or regenerate + trigger: | + - Gate 2 PASSED + - Ready to generate production template file --- # Regulatory Templates - Gate 3: Template File Generation diff --git a/finops-team/skills/regulatory-templates-setup/SKILL.md b/finops-team/skills/regulatory-templates-setup/SKILL.md index 470a6649..6de06382 100644 --- a/finops-team/skills/regulatory-templates-setup/SKILL.md +++ b/finops-team/skills/regulatory-templates-setup/SKILL.md @@ -1,25 +1,23 @@ --- -name: ring:regulatory-templates-setup +name: regulatory-templates-setup description: | Initial setup sub-skill - handles template selection and context initialization for the 5-stage regulatory workflow. Supports any regulatory template (pre-defined or new) via official spec intake (URL/XSD/PDF). - -dependencies: [] - -role: setup - -trigger: | - - Called by regulatory-templates orchestrator at workflow start - - Need to select template type and initialize context - -skip_when: | - - Not in regulatory-templates workflow - - Setup already completed for current template - -sequence: - after: [regulatory-templates] - before: [regulatory-templates-gate1] +metadata: + dependencies: [] + role: setup + sequence: + after: + - regulatory-templates + before: + - regulatory-templates-gate1 + skip_when: | + - Not in regulatory-templates workflow + - Setup already completed for current template + trigger: | + - Called by regulatory-templates orchestrator at workflow start + - Need to select template type and initialize context --- # Regulatory Templates - Initial Setup diff --git a/finops-team/skills/regulatory-templates/SKILL.md b/finops-team/skills/regulatory-templates/SKILL.md index f5642e61..9fa9486c 100644 --- a/finops-team/skills/regulatory-templates/SKILL.md +++ b/finops-team/skills/regulatory-templates/SKILL.md @@ -1,33 +1,30 @@ --- -name: ring:regulatory-templates +name: regulatory-templates description: | 5-stage regulatory template orchestrator - manages setup, Gate 1 (analysis + auto-save), Gate 2 (validation), Gate 3 (generation), optional Test Gate, optional Contribution Gate. Supports any regulatory template (BACEN, RFB, CVM, SUSEP, COAF, or other). - -dependencies: +metadata: + dependencies: - ring:regulatory-templates-setup - ring:regulatory-templates-gate1 - ring:regulatory-templates-gate2 - ring:regulatory-templates-gate3 - ring:finops-analyzer - ring:finops-automation - -role: orchestrator - -trigger: | - - Creating BACEN CADOCs (4010, 4016, 4111, or any other) - - Mapping e-Financeira, DIMP, APIX templates - - Full automation from analysis to template creation - - Creating any new regulatory template not yet in registry - -skip_when: | - - Non-Brazilian regulations → not applicable - - Analysis-only without template → use finops-analyzer directly - - Template already exists, just needs updates → modify directly - -sequence: - before: [regulatory-templates-setup] + role: orchestrator + sequence: + before: + - regulatory-templates-setup + skip_when: | + - Non-Brazilian regulations → not applicable + - Analysis-only without template → use finops-analyzer directly + - Template already exists, just needs updates → modify directly + trigger: | + - Creating BACEN CADOCs (4010, 4016, 4111, or any other) + - Mapping e-Financeira, DIMP, APIX templates + - Full automation from analysis to template creation + - Creating any new regulatory template not yet in registry --- # Regulatory Templates - Orchestrator diff --git a/finops-team/skills/using-finops-team/SKILL.md b/finops-team/skills/using-finops-team/SKILL.md index 4d9aafe7..5bd1e471 100644 --- a/finops-team/skills/using-finops-team/SKILL.md +++ b/finops-team/skills/using-finops-team/SKILL.md @@ -1,30 +1,27 @@ --- -name: ring:using-finops-team +name: using-finops-team description: | 3 FinOps agents: 2 for Brazilian financial regulatory compliance (BACEN, RFB, Open Banking), 1 for infrastructure cost estimation when onboarding customers. Supports any regulatory template via open intake system. - -dependencies: +metadata: + dependencies: - ring:finops-analyzer - ring:finops-automation - ring:infrastructure-cost-estimator - ring:regulatory-templates - -role: guide - -trigger: | - - Brazilian regulatory reporting (BACEN, RFB) - - Financial compliance requirements - - Open Banking specifications - - Template generation for Reporter platform - - Infrastructure cost estimation for new customers - - AWS capacity planning and pricing - -skip_when: | - - Non-Brazilian regulations → use appropriate resources - - Non-AWS infrastructure → adapt formulas - - One-time cost question → direct calculation + role: guide + skip_when: |- + - Non-Brazilian regulations → use appropriate resources + - Non-AWS infrastructure → adapt formulas + - One-time cost question → direct calculation + trigger: | + - Brazilian regulatory reporting (BACEN, RFB) + - Financial compliance requirements + - Open Banking specifications + - Template generation for Reporter platform + - Infrastructure cost estimation for new customers + - AWS capacity planning and pricing --- # Using Ring FinOps & Regulatory Agents diff --git a/pm-team/skills/delivery-status-tracking/SKILL.md b/pm-team/skills/delivery-status-tracking/SKILL.md index 1e6a2746..cfb4f891 100644 --- a/pm-team/skills/delivery-status-tracking/SKILL.md +++ b/pm-team/skills/delivery-status-tracking/SKILL.md @@ -1,24 +1,25 @@ --- -name: ring:delivery-status-tracking +name: delivery-status-tracking description: | Delivery status tracking and progress reporting. Analyzes repository against delivery roadmap to calculate actual vs planned progress, identify delays, and provide insights on velocity and risk trends. - -trigger: | - - Delivery roadmap exists (from ring:pre-dev-delivery-planning) - - Need to check progress against plan - - Stakeholders requesting status update - - Regular checkpoint (weekly/sprint end) - -skip_when: | - - No delivery roadmap → create one first with ring:pre-dev-delivery-planning - - Planning phase only → execute tasks first - - No repository activity → nothing to analyze - -sequence: - after: [ring:pre-dev-delivery-planning, ring:executing-plans, ring:dev-cycle] - before: [] +metadata: + sequence: + after: + - ring:pre-dev-delivery-planning + - ring:executing-plans + - ring:dev-cycle + before: [] + skip_when: | + - No delivery roadmap → create one first with ring:pre-dev-delivery-planning + - Planning phase only → execute tasks first + - No repository activity → nothing to analyze + trigger: | + - Delivery roadmap exists (from ring:pre-dev-delivery-planning) + - Need to check progress against plan + - Stakeholders requesting status update + - Regular checkpoint (weekly/sprint end) --- # Delivery Status Tracking - Evidence-Based Progress Reporting diff --git a/pm-team/skills/pre-dev-api-design/SKILL.md b/pm-team/skills/pre-dev-api-design/SKILL.md index 707554fc..f26fc266 100644 --- a/pm-team/skills/pre-dev-api-design/SKILL.md +++ b/pm-team/skills/pre-dev-api-design/SKILL.md @@ -1,23 +1,23 @@ --- -name: ring:pre-dev-api-design +name: pre-dev-api-design description: | Gate 4: API contracts document - defines component interfaces and data contracts before protocol/technology selection. Large Track only. - -trigger: | - - TRD passed Gate 3 validation - - System has multiple components that need to integrate - - Building APIs (internal or external) - - Large Track workflow (2+ day features) - -skip_when: | - - Small Track workflow → skip to Task Breakdown - - Single component system → skip to Data Model - - TRD not validated → complete Gate 3 first - -sequence: - after: [ring:pre-dev-trd-creation] - before: [ring:pre-dev-data-model] +metadata: + sequence: + after: + - ring:pre-dev-trd-creation + before: + - ring:pre-dev-data-model + skip_when: | + - Small Track workflow → skip to Task Breakdown + - Single component system → skip to Data Model + - TRD not validated → complete Gate 3 first + trigger: | + - TRD passed Gate 3 validation + - System has multiple components that need to integrate + - Building APIs (internal or external) + - Large Track workflow (2+ day features) --- # API/Contract Design - Defining Component Interfaces diff --git a/pm-team/skills/pre-dev-data-model/SKILL.md b/pm-team/skills/pre-dev-data-model/SKILL.md index feb51938..40f8e93a 100644 --- a/pm-team/skills/pre-dev-data-model/SKILL.md +++ b/pm-team/skills/pre-dev-data-model/SKILL.md @@ -1,23 +1,23 @@ --- -name: ring:pre-dev-data-model +name: pre-dev-data-model description: | Gate 5: Data structures document - defines entities, relationships, and ownership before database technology selection. Large Track only. - -trigger: | - - API Design passed Gate 4 validation - - System stores persistent data - - Multiple entities with relationships - - Large Track workflow (2+ day features) - -skip_when: | - - Small Track workflow → skip to Task Breakdown - - No persistent data → skip to Dependency Map - - API Design not validated → complete Gate 4 first - -sequence: - after: [ring:pre-dev-api-design] - before: [ring:pre-dev-dependency-map] +metadata: + sequence: + after: + - ring:pre-dev-api-design + before: + - ring:pre-dev-dependency-map + skip_when: | + - Small Track workflow → skip to Task Breakdown + - No persistent data → skip to Dependency Map + - API Design not validated → complete Gate 4 first + trigger: | + - API Design passed Gate 4 validation + - System stores persistent data + - Multiple entities with relationships + - Large Track workflow (2+ day features) --- # Data Modeling - Defining Data Structures diff --git a/pm-team/skills/pre-dev-delivery-planning/SKILL.md b/pm-team/skills/pre-dev-delivery-planning/SKILL.md index 044d5d3d..353f343a 100644 --- a/pm-team/skills/pre-dev-delivery-planning/SKILL.md +++ b/pm-team/skills/pre-dev-delivery-planning/SKILL.md @@ -1,24 +1,26 @@ --- -name: ring:pre-dev-delivery-planning +name: pre-dev-delivery-planning description: | Gate 9 (Full Track) / Gate 4 (Small Track): Delivery roadmap and timeline planning. Transforms tasks into realistic delivery schedule with critical path analysis, resource allocation, and delivery breakdown. MANDATORY gate for both workflows. - -trigger: | - - Tasks passed Gate 7 validation (Full Track) OR Gate 3 (Small Track) - - Need realistic delivery timeline with dates - - Ready to convert tasks into delivery schedule - - Team composition known or determinable - -skip_when: | - - Tasks not validated → complete task breakdown first - - Proof-of-concept without delivery commitment - - Research/exploration work without delivery deadline - -sequence: - after: [ring:pre-dev-task-breakdown, ring:pre-dev-subtask-creation] - before: [ring:executing-plans, ring:dev-cycle] +metadata: + sequence: + after: + - ring:pre-dev-task-breakdown + - ring:pre-dev-subtask-creation + before: + - ring:executing-plans + - ring:dev-cycle + skip_when: | + - Tasks not validated → complete task breakdown first + - Proof-of-concept without delivery commitment + - Research/exploration work without delivery deadline + trigger: | + - Tasks passed Gate 7 validation (Full Track) OR Gate 3 (Small Track) + - Need realistic delivery timeline with dates + - Ready to convert tasks into delivery schedule + - Team composition known or determinable --- # Delivery Planning - Realistic Roadmap with Critical Path diff --git a/pm-team/skills/pre-dev-dependency-map/SKILL.md b/pm-team/skills/pre-dev-dependency-map/SKILL.md index 6574c4df..692f4eca 100644 --- a/pm-team/skills/pre-dev-dependency-map/SKILL.md +++ b/pm-team/skills/pre-dev-dependency-map/SKILL.md @@ -1,24 +1,24 @@ --- -name: ring:pre-dev-dependency-map +name: pre-dev-dependency-map description: | Gate 6: Technology choices document - explicit, versioned, validated technology selections with justifications. Large Track only. HARD BLOCK: Must load Ring Standards and PROJECT_RULES.md before proceeding. - -trigger: | - - Data Model passed Gate 5 validation - - About to select specific technologies - - Tempted to write "@latest" or "newest version" - - Large Track workflow (2+ day features) - -skip_when: | - - Small Track workflow → skip to Task Breakdown - - Technologies already locked → skip to Task Breakdown - - Data Model not validated → complete Gate 5 first - -sequence: - after: [ring:pre-dev-data-model] - before: [ring:pre-dev-task-breakdown] +metadata: + sequence: + after: + - ring:pre-dev-data-model + before: + - ring:pre-dev-task-breakdown + skip_when: | + - Small Track workflow → skip to Task Breakdown + - Technologies already locked → skip to Task Breakdown + - Data Model not validated → complete Gate 5 first + trigger: | + - Data Model passed Gate 5 validation + - About to select specific technologies + - Tempted to write "@latest" or "newest version" + - Large Track workflow (2+ day features) --- # Dependency Map - Explicit Technology Choices diff --git a/pm-team/skills/pre-dev-design-validation/SKILL.md b/pm-team/skills/pre-dev-design-validation/SKILL.md index 5003016f..d378bb3b 100644 --- a/pm-team/skills/pre-dev-design-validation/SKILL.md +++ b/pm-team/skills/pre-dev-design-validation/SKILL.md @@ -1,24 +1,25 @@ --- -name: ring:pre-dev-design-validation +name: pre-dev-design-validation description: | Gate 1.5/2.5: Design Validation - verifies UX specifications are complete before proceeding to technical architecture. Checklist-based validation that prevents incomplete designs from reaching implementation. - -trigger: | - - After PRD + UX criteria created (Gate 1) - - After Feature Map + UX Design created (Gate 2, Large track) - - Before starting TRD (Gate 3) - - User asks to "validate design" or "check if design is complete" - -skip_when: | - - Feature is backend-only with no UI - - Pure API/infrastructure task - - Bug fix with no UX changes - -sequence: - after: [ring:pre-dev-prd-creation, ring:pre-dev-feature-map] - before: [ring:pre-dev-trd-creation] +metadata: + sequence: + after: + - ring:pre-dev-prd-creation + - ring:pre-dev-feature-map + before: + - ring:pre-dev-trd-creation + skip_when: | + - Feature is backend-only with no UI + - Pure API/infrastructure task + - Bug fix with no UX changes + trigger: | + - After PRD + UX criteria created (Gate 1) + - After Feature Map + UX Design created (Gate 2, Large track) + - Before starting TRD (Gate 3) + - User asks to "validate design" or "check if design is complete" --- # Design Validation Gate diff --git a/pm-team/skills/pre-dev-feature-map/SKILL.md b/pm-team/skills/pre-dev-feature-map/SKILL.md index 74e2f242..85688357 100644 --- a/pm-team/skills/pre-dev-feature-map/SKILL.md +++ b/pm-team/skills/pre-dev-feature-map/SKILL.md @@ -1,23 +1,23 @@ --- -name: ring:pre-dev-feature-map +name: pre-dev-feature-map description: | Gate 2: Feature relationship map - visualizes feature landscape, groupings, and interactions at business level before technical architecture. - -trigger: | - - PRD passed Gate 1 validation - - Multiple features with complex interactions - - Need to understand feature scope and relationships - - Large Track workflow (2+ day features) - -skip_when: | - - Small Track workflow (<2 days) → skip to TRD - - Single simple feature → TRD directly - - PRD not validated → complete Gate 1 first - -sequence: - after: [ring:pre-dev-prd-creation] - before: [ring:pre-dev-trd-creation] +metadata: + sequence: + after: + - ring:pre-dev-prd-creation + before: + - ring:pre-dev-trd-creation + skip_when: | + - Small Track workflow (<2 days) → skip to TRD + - Single simple feature → TRD directly + - PRD not validated → complete Gate 1 first + trigger: | + - PRD passed Gate 1 validation + - Multiple features with complex interactions + - Need to understand feature scope and relationships + - Large Track workflow (2+ day features) --- # Feature Map Creation - Understanding the Feature Landscape diff --git a/pm-team/skills/pre-dev-feature/SKILL.md b/pm-team/skills/pre-dev-feature/SKILL.md index 6edbb44d..23d8c7c4 100644 --- a/pm-team/skills/pre-dev-feature/SKILL.md +++ b/pm-team/skills/pre-dev-feature/SKILL.md @@ -1,47 +1,39 @@ --- -name: ring:pre-dev-feature +name: pre-dev-feature description: | Lightweight 5-gate pre-dev workflow for small features (<2 days). Orchestrates topology discovery, research, PRD with UX validation, design validation, TRD, task breakdown, and delivery planning in a sequential gated process with human approval at each gate. - -trigger: | - - Feature takes <2 days to implement - - Uses existing architecture patterns - - Doesn't add new external dependencies - - Doesn't create new data models/entities - - Doesn't require multi-service integration - - Can be completed by a single developer - -skip_when: | - - Feature is complex (>=2 days) - use ring:pre-dev-full instead - - Adds new dependencies, data models, or architecture patterns - -sequence: - before: [ring:write-plan, ring:dev-cycle] - -related: - complementary: [ring:pre-dev-full, ring:write-plan, ring:worktree] - skills_orchestrated: +allowed-tools: Skill, Read, Write, Glob, Grep, Bash, Agent, AskUserQuestion +metadata: + related: + complementary: + - ring:pre-dev-full + - ring:write-plan + - ring:worktree + skills_orchestrated: - ring:pre-dev-research - ring:pre-dev-prd-creation - ring:pre-dev-design-validation - ring:pre-dev-trd-creation - ring:pre-dev-task-breakdown - ring:pre-dev-delivery-planning - -user_invocable: false - -allowed-tools: - - Skill - - Read - - Write - - Glob - - Grep - - Bash - - Agent - - AskUserQuestion + sequence: + before: + - ring:write-plan + - ring:dev-cycle + skip_when: | + - Feature is complex (>=2 days) - use ring:pre-dev-full instead + - Adds new dependencies, data models, or architecture patterns + trigger: | + - Feature takes <2 days to implement + - Uses existing architecture patterns + - Doesn't add new external dependencies + - Doesn't create new data models/entities + - Doesn't require multi-service integration + - Can be completed by a single developer + user_invocable: false --- # Small Track Pre-Dev Workflow (5 Gates) diff --git a/pm-team/skills/pre-dev-full/SKILL.md b/pm-team/skills/pre-dev-full/SKILL.md index ed6779b8..c593aba6 100644 --- a/pm-team/skills/pre-dev-full/SKILL.md +++ b/pm-team/skills/pre-dev-full/SKILL.md @@ -1,29 +1,18 @@ --- -name: ring:pre-dev-full +name: pre-dev-full description: | Complete 10-gate pre-dev workflow for large features (>=2 days). Orchestrates topology discovery, research, PRD, feature map, design validation, TRD, API design, data model, dependency map, task breakdown, subtask creation, and delivery planning in a sequential gated process with human approval at each gate. - -trigger: | - - Feature takes >=2 days to implement - - Adds new external dependencies (APIs, databases, libraries) - - Creates new data models or entities - - Requires multi-service integration - - Uses new architecture patterns - - Requires team collaboration - -skip_when: | - - Feature is simple (<2 days, existing patterns) - use ring:pre-dev-feature instead - - No new dependencies, data models, or architecture patterns needed - -sequence: - before: [ring:write-plan, ring:dev-cycle] - -related: - complementary: [ring:pre-dev-feature, ring:write-plan, ring:worktree] - skills_orchestrated: +allowed-tools: Skill, Read, Write, Glob, Grep, Bash, Agent, AskUserQuestion +metadata: + related: + complementary: + - ring:pre-dev-feature + - ring:write-plan + - ring:worktree + skills_orchestrated: - ring:pre-dev-research - ring:pre-dev-prd-creation - ring:pre-dev-feature-map @@ -35,18 +24,21 @@ related: - ring:pre-dev-task-breakdown - ring:pre-dev-subtask-creation - ring:pre-dev-delivery-planning - -user_invocable: false - -allowed-tools: - - Skill - - Read - - Write - - Glob - - Grep - - Bash - - Agent - - AskUserQuestion + sequence: + before: + - ring:write-plan + - ring:dev-cycle + skip_when: | + - Feature is simple (<2 days, existing patterns) - use ring:pre-dev-feature instead + - No new dependencies, data models, or architecture patterns needed + trigger: | + - Feature takes >=2 days to implement + - Adds new external dependencies (APIs, databases, libraries) + - Creates new data models or entities + - Requires multi-service integration + - Uses new architecture patterns + - Requires team collaboration + user_invocable: false --- # Full Track Pre-Dev Workflow (10 Gates) diff --git a/pm-team/skills/pre-dev-prd-creation/SKILL.md b/pm-team/skills/pre-dev-prd-creation/SKILL.md index 63c0e632..e97eb79f 100644 --- a/pm-team/skills/pre-dev-prd-creation/SKILL.md +++ b/pm-team/skills/pre-dev-prd-creation/SKILL.md @@ -1,22 +1,22 @@ --- -name: ring:pre-dev-prd-creation +name: pre-dev-prd-creation description: | Gate 1: Business requirements document - defines WHAT/WHY before HOW. Creates PRD with problem definition, user stories, success metrics. - -trigger: | - - Starting new product or major feature - - User asks to "plan", "design", or "architect" - - About to write code without documented requirements - - Asked to create PRD or requirements document - -skip_when: | - - PRD already exists and validated → proceed to Gate 2 - - Pure technical task without business impact → TRD directly - - Bug fix → systematic-debugging - -sequence: - before: [ring:pre-dev-feature-map, ring:pre-dev-trd-creation] +metadata: + sequence: + before: + - ring:pre-dev-feature-map + - ring:pre-dev-trd-creation + skip_when: | + - PRD already exists and validated → proceed to Gate 2 + - Pure technical task without business impact → TRD directly + - Bug fix → systematic-debugging + trigger: | + - Starting new product or major feature + - User asks to "plan", "design", or "architect" + - About to write code without documented requirements + - Asked to create PRD or requirements document --- # PRD Creation - Business Before Technical diff --git a/pm-team/skills/pre-dev-research/SKILL.md b/pm-team/skills/pre-dev-research/SKILL.md index b9d7fb8f..75042f43 100644 --- a/pm-team/skills/pre-dev-research/SKILL.md +++ b/pm-team/skills/pre-dev-research/SKILL.md @@ -1,43 +1,50 @@ --- -name: ring:pre-dev-research +name: pre-dev-research description: | Gate 0 research phase for pre-dev workflow. Dispatches 4 parallel research agents to gather codebase patterns, external best practices, framework documentation, and UX/product research BEFORE creating PRD/TRD. Outputs research.md with file:line references and user research findings. - -trigger: | - - Before any pre-dev workflow (Gate 0) - - When planning new features or modifications - - Invoked by /ring:pre-dev-full and /ring:pre-dev-feature - -skip_when: | - - Trivial changes that don't need planning - - Research already completed (research.md exists and is recent) - -sequence: - before: [ring:pre-dev-prd-creation, ring:pre-dev-feature-map] - -related: - complementary: [ring:pre-dev-prd-creation, ring:pre-dev-trd-creation] - -research_modes: - greenfield: - description: "New feature with no existing patterns to follow" - primary_agents: [ring:best-practices-researcher, ring:framework-docs-researcher, ring:product-designer] - focus: "External best practices, framework patterns, and user problem validation" - - modification: - description: "Changing or extending existing functionality" - primary_agents: [ring:repo-research-analyst] - secondary_agents: [ring:product-designer] - focus: "Existing codebase patterns and conventions, UX impact assessment" - - integration: - description: "Connecting systems or adding external dependencies" - primary_agents: [ring:framework-docs-researcher, ring:best-practices-researcher, ring:repo-research-analyst] - secondary_agents: [ring:product-designer] - focus: "API documentation, integration patterns, and user experience considerations" +metadata: + related: + complementary: + - ring:pre-dev-prd-creation + - ring:pre-dev-trd-creation + research_modes: + greenfield: + description: New feature with no existing patterns to follow + primary_agents: + - ring:best-practices-researcher + - ring:framework-docs-researcher + - ring:product-designer + focus: External best practices, framework patterns, and user problem validation + modification: + description: Changing or extending existing functionality + primary_agents: + - ring:repo-research-analyst + secondary_agents: + - ring:product-designer + focus: Existing codebase patterns and conventions, UX impact assessment + integration: + description: Connecting systems or adding external dependencies + primary_agents: + - ring:framework-docs-researcher + - ring:best-practices-researcher + - ring:repo-research-analyst + secondary_agents: + - ring:product-designer + focus: API documentation, integration patterns, and user experience considerations + sequence: + before: + - ring:pre-dev-prd-creation + - ring:pre-dev-feature-map + skip_when: | + - Trivial changes that don't need planning + - Research already completed (research.md exists and is recent) + trigger: | + - Before any pre-dev workflow (Gate 0) + - When planning new features or modifications + - Invoked by /ring:pre-dev-full and /ring:pre-dev-feature --- # Pre-Dev Research Skill (Gate 0) diff --git a/pm-team/skills/pre-dev-subtask-creation/SKILL.md b/pm-team/skills/pre-dev-subtask-creation/SKILL.md index da25c587..8dc4f8cc 100644 --- a/pm-team/skills/pre-dev-subtask-creation/SKILL.md +++ b/pm-team/skills/pre-dev-subtask-creation/SKILL.md @@ -1,23 +1,24 @@ --- -name: ring:pre-dev-subtask-creation +name: pre-dev-subtask-creation description: | Gate 8: Zero-context implementation steps - 2-5 minute atomic subtasks with complete code, exact commands, TDD pattern. Large Track only. - -trigger: | - - Tasks passed Gate 7 validation - - Need absolute implementation clarity - - Creating work for engineers with zero codebase context - - Large Track workflow (2+ day features) - -skip_when: | - - Small Track workflow → execute tasks directly - - Tasks simple enough without breakdown - - Tasks not validated → complete Gate 7 first - -sequence: - after: [ring:pre-dev-task-breakdown] - before: [ring:executing-plans, ring:subagent-driven-development] +metadata: + sequence: + after: + - ring:pre-dev-task-breakdown + before: + - ring:executing-plans + - ring:subagent-driven-development + skip_when: | + - Small Track workflow → execute tasks directly + - Tasks simple enough without breakdown + - Tasks not validated → complete Gate 7 first + trigger: | + - Tasks passed Gate 7 validation + - Need absolute implementation clarity + - Creating work for engineers with zero codebase context + - Large Track workflow (2+ day features) --- # Subtask Creation - Bite-Sized, Zero-Context Steps diff --git a/pm-team/skills/pre-dev-task-breakdown/SKILL.md b/pm-team/skills/pre-dev-task-breakdown/SKILL.md index 3e5b9f32..848beb1d 100644 --- a/pm-team/skills/pre-dev-task-breakdown/SKILL.md +++ b/pm-team/skills/pre-dev-task-breakdown/SKILL.md @@ -1,23 +1,25 @@ --- -name: ring:pre-dev-task-breakdown +name: pre-dev-task-breakdown description: | Gate 7: Implementation tasks - value-driven decomposition into working increments that deliver measurable user value. - -trigger: | - - PRD passed Gate 1 (required) - - TRD passed Gate 3 (required) - - All Large Track gates passed (if applicable) - - Ready to create sprint/iteration tasks - -skip_when: | - - PRD or TRD not validated → complete earlier gates - - Tasks already exist → proceed to Subtask Creation - - Trivial change → direct implementation - -sequence: - after: [ring:pre-dev-trd-creation, ring:pre-dev-dependency-map] - before: [ring:pre-dev-subtask-creation, ring:executing-plans] +metadata: + sequence: + after: + - ring:pre-dev-trd-creation + - ring:pre-dev-dependency-map + before: + - ring:pre-dev-subtask-creation + - ring:executing-plans + skip_when: | + - PRD or TRD not validated → complete earlier gates + - Tasks already exist → proceed to Subtask Creation + - Trivial change → direct implementation + trigger: | + - PRD passed Gate 1 (required) + - TRD passed Gate 3 (required) + - All Large Track gates passed (if applicable) + - Ready to create sprint/iteration tasks --- # Task Breakdown - Value-Driven Decomposition diff --git a/pm-team/skills/pre-dev-trd-creation/SKILL.md b/pm-team/skills/pre-dev-trd-creation/SKILL.md index 7cd7f5b2..dbf196f5 100644 --- a/pm-team/skills/pre-dev-trd-creation/SKILL.md +++ b/pm-team/skills/pre-dev-trd-creation/SKILL.md @@ -1,25 +1,28 @@ --- -name: ring:pre-dev-trd-creation +name: pre-dev-trd-creation description: | Gate 3: Technical architecture document - defines HOW/WHERE with technology-agnostic patterns before concrete implementation choices. - -trigger: | - - PRD passed Gate 1 (required) - - Feature Map passed Gate 2 (if Large Track) - - Design Validation passed Gate 1.5/2.5 (if feature has UI) - - About to design technical architecture - - Tempted to specify "PostgreSQL" instead of "Relational Database" - -skip_when: | - - PRD not validated → complete Gate 1 first - - Design Validation not passed (for UI features) → complete Gate 1.5/2.5 first - - Architecture already documented → proceed to API Design - - Pure business requirement change → update PRD - -sequence: - after: [ring:pre-dev-prd-creation, ring:pre-dev-feature-map, ring:pre-dev-design-validation] - before: [ring:pre-dev-api-design, ring:pre-dev-task-breakdown] +metadata: + sequence: + after: + - ring:pre-dev-prd-creation + - ring:pre-dev-feature-map + - ring:pre-dev-design-validation + before: + - ring:pre-dev-api-design + - ring:pre-dev-task-breakdown + skip_when: | + - PRD not validated → complete Gate 1 first + - Design Validation not passed (for UI features) → complete Gate 1.5/2.5 first + - Architecture already documented → proceed to API Design + - Pure business requirement change → update PRD + trigger: | + - PRD passed Gate 1 (required) + - Feature Map passed Gate 2 (if Large Track) + - Design Validation passed Gate 1.5/2.5 (if feature has UI) + - About to design technical architecture + - Tempted to specify "PostgreSQL" instead of "Relational Database" --- # TRD Creation - Architecture Before Implementation diff --git a/pm-team/skills/using-pm-team/SKILL.md b/pm-team/skills/using-pm-team/SKILL.md index 5e70e084..abae68c4 100644 --- a/pm-team/skills/using-pm-team/SKILL.md +++ b/pm-team/skills/using-pm-team/SKILL.md @@ -1,18 +1,17 @@ --- -name: ring:using-pm-team +name: using-pm-team description: | 12 pre-dev workflow skills + 4 research agents organized into Small Track (4 gates, <2 days) and Large Track (9 gates, 2+ days) for systematic feature planning with research-first approach. - -trigger: | - - Starting any feature implementation - - Need systematic planning before coding - - User requests "plan a feature" - -skip_when: | - - Quick exploratory work → ring:brainstorming may suffice - - Bug fix with known solution → direct implementation - - Trivial change (<1 hour) → skip formal planning +metadata: + skip_when: |- + - Quick exploratory work → ring:brainstorming may suffice + - Bug fix with known solution → direct implementation + - Trivial change (<1 hour) → skip formal planning + trigger: | + - Starting any feature implementation + - Need systematic planning before coding + - User requests "plan a feature" --- # Using Ring Team-Product: Pre-Dev Workflow & Delivery Tracking diff --git a/pmo-team/skills/delivery-reporting/SKILL.md b/pmo-team/skills/delivery-reporting/SKILL.md index 1fcf1630..b2348f42 100644 --- a/pmo-team/skills/delivery-reporting/SKILL.md +++ b/pmo-team/skills/delivery-reporting/SKILL.md @@ -4,20 +4,20 @@ description: | Delivery reporting skill for creating visual executive presentations of squad deliveries (engineering, product, design). Analyzes Git repositories to extract business value from technical changes and generates HTML slide presentations with customizable visual identity. - -trigger: | - - Need squad delivery report (eng + product + design) - - Showcase releases and features to executives - - Quarterly/monthly delivery summary - - Client/stakeholder delivery showcase - -skip_when: | - - Portfolio/project status → use executive-reporting - - Risk/resource analysis → use risk-management/resource-allocation - - Technical documentation → use ring-tw-team - -related: - complementary: [executive-reporting, portfolio-planning] +metadata: + related: + complementary: + - executive-reporting + - portfolio-planning + skip_when: | + - Portfolio/project status → use executive-reporting + - Risk/resource analysis → use risk-management/resource-allocation + - Technical documentation → use ring-tw-team + trigger: | + - Need squad delivery report (eng + product + design) + - Showcase releases and features to executives + - Quarterly/monthly delivery summary + - Client/stakeholder delivery showcase --- # Delivery Reporting Skill diff --git a/pmo-team/skills/dependency-mapping/SKILL.md b/pmo-team/skills/dependency-mapping/SKILL.md index 9b3cc3b1..998c79d5 100644 --- a/pmo-team/skills/dependency-mapping/SKILL.md +++ b/pmo-team/skills/dependency-mapping/SKILL.md @@ -1,22 +1,22 @@ --- -name: ring:dependency-mapping +name: dependency-mapping description: | Cross-project dependency mapping and analysis skill for identifying, tracking, and managing dependencies across portfolio projects. - -trigger: | - - Need to map project dependencies - - Dependency conflict identified - - Planning new project with dependencies - - Critical path analysis needed - -skip_when: | - - Single project internal dependencies → handle in project scope - - Resource dependencies only → use resource-allocation - - Risk from dependencies → use risk-management - -related: - complementary: [portfolio-planning, risk-management] +metadata: + related: + complementary: + - portfolio-planning + - risk-management + skip_when: | + - Single project internal dependencies → handle in project scope + - Resource dependencies only → use resource-allocation + - Risk from dependencies → use risk-management + trigger: | + - Need to map project dependencies + - Dependency conflict identified + - Planning new project with dependencies + - Critical path analysis needed --- # Dependency Mapping Skill diff --git a/pmo-team/skills/executive-reporting/SKILL.md b/pmo-team/skills/executive-reporting/SKILL.md index de58549b..5928de4d 100644 --- a/pmo-team/skills/executive-reporting/SKILL.md +++ b/pmo-team/skills/executive-reporting/SKILL.md @@ -1,22 +1,22 @@ --- -name: ring:executive-reporting +name: executive-reporting description: | Executive communication and reporting skill for creating dashboards, status summaries, and board packages. Focuses on actionable insights for leadership. - -trigger: | - - Need executive status update - - Board meeting preparation - - Portfolio dashboard creation - - Stakeholder escalation report - -skip_when: | - - Detailed project analysis → use project-health-check - - Technical documentation → use ring-tw-team - - Financial deep dive → use ring-finops-team - -related: - complementary: [portfolio-planning, project-health-check] +metadata: + related: + complementary: + - portfolio-planning + - project-health-check + skip_when: | + - Detailed project analysis → use project-health-check + - Technical documentation → use ring-tw-team + - Financial deep dive → use ring-finops-team + trigger: | + - Need executive status update + - Board meeting preparation + - Portfolio dashboard creation + - Stakeholder escalation report --- # Executive Reporting Skill diff --git a/pmo-team/skills/pmo-retrospective/SKILL.md b/pmo-team/skills/pmo-retrospective/SKILL.md index bfdb2a99..c1696672 100644 --- a/pmo-team/skills/pmo-retrospective/SKILL.md +++ b/pmo-team/skills/pmo-retrospective/SKILL.md @@ -1,22 +1,22 @@ --- -name: ring:pmo-retrospective +name: pmo-retrospective description: | Portfolio retrospective skill for capturing lessons learned, process improvements, and organizational learning across completed projects. - -trigger: | - - Project closure requiring retrospective - - Portfolio period review (quarterly/annual) - - Process improvement initiative - - Pattern of issues recurring - -skip_when: | - - Sprint retrospective → team-level, not PMO - - Technical post-mortem → use ring-dev-team - - Single incident analysis → handle in project scope - -related: - complementary: [portfolio-planning, project-health-check] +metadata: + related: + complementary: + - portfolio-planning + - project-health-check + skip_when: | + - Sprint retrospective → team-level, not PMO + - Technical post-mortem → use ring-dev-team + - Single incident analysis → handle in project scope + trigger: | + - Project closure requiring retrospective + - Portfolio period review (quarterly/annual) + - Process improvement initiative + - Pattern of issues recurring --- # PMO Retrospective Skill diff --git a/pmo-team/skills/portfolio-planning/SKILL.md b/pmo-team/skills/portfolio-planning/SKILL.md index 5bcc589c..09cbf9d1 100644 --- a/pmo-team/skills/portfolio-planning/SKILL.md +++ b/pmo-team/skills/portfolio-planning/SKILL.md @@ -1,23 +1,25 @@ --- -name: ring:portfolio-planning +name: portfolio-planning description: | Strategic portfolio planning skill for multi-project coordination, capacity assessment, and portfolio optimization. Provides framework for portfolio-level decision making. - -trigger: | - - Need to assess portfolio health - - Planning portfolio for next quarter/year - - Evaluating new project against portfolio - - Rebalancing portfolio priorities - -skip_when: | - - Single project planning → use ring:pre-dev-feature - - Immediate status report → use executive-reporting - - Resource-only analysis → use resource-allocation - -related: - similar: [ring:pre-dev-feature] - complementary: [resource-allocation, risk-management, executive-reporting] +metadata: + related: + similar: + - ring:pre-dev-feature + complementary: + - resource-allocation + - risk-management + - executive-reporting + skip_when: | + - Single project planning → use ring:pre-dev-feature + - Immediate status report → use executive-reporting + - Resource-only analysis → use resource-allocation + trigger: | + - Need to assess portfolio health + - Planning portfolio for next quarter/year + - Evaluating new project against portfolio + - Rebalancing portfolio priorities --- # Portfolio Planning Skill diff --git a/pmo-team/skills/project-health-check/SKILL.md b/pmo-team/skills/project-health-check/SKILL.md index 8ff773cb..04a17f86 100644 --- a/pmo-team/skills/project-health-check/SKILL.md +++ b/pmo-team/skills/project-health-check/SKILL.md @@ -1,22 +1,22 @@ --- -name: ring:project-health-check +name: project-health-check description: | Individual project health assessment skill for evaluating project status across multiple dimensions. Provides early warning of troubled projects. - -trigger: | - - Need to assess single project health - - Project showing warning signs - - Milestone review required - - Stakeholder escalation received - -skip_when: | - - Portfolio-level view → use portfolio-planning - - Resource-only issue → use resource-allocation - - Risk-only analysis → use risk-management - -related: - complementary: [portfolio-planning, risk-management] +metadata: + related: + complementary: + - portfolio-planning + - risk-management + skip_when: | + - Portfolio-level view → use portfolio-planning + - Resource-only issue → use resource-allocation + - Risk-only analysis → use risk-management + trigger: | + - Need to assess single project health + - Project showing warning signs + - Milestone review required + - Stakeholder escalation received --- # Project Health Check Skill diff --git a/pmo-team/skills/resource-allocation/SKILL.md b/pmo-team/skills/resource-allocation/SKILL.md index 4c281e7e..f03ad484 100644 --- a/pmo-team/skills/resource-allocation/SKILL.md +++ b/pmo-team/skills/resource-allocation/SKILL.md @@ -1,22 +1,22 @@ --- -name: ring:resource-allocation +name: resource-allocation description: | Resource capacity planning and allocation skill for managing people and skills across multiple projects. Identifies conflicts, gaps, and optimization opportunities. - -trigger: | - - Need to allocate resources to projects - - Capacity planning for upcoming work - - Resource conflict resolution - - Skills gap analysis - -skip_when: | - - Single project staffing → use ring-pm-team - - Cost analysis → use ring-finops-team - - Project status → use project-health-check - -related: - complementary: [portfolio-planning, risk-management] +metadata: + related: + complementary: + - portfolio-planning + - risk-management + skip_when: | + - Single project staffing → use ring-pm-team + - Cost analysis → use ring-finops-team + - Project status → use project-health-check + trigger: | + - Need to allocate resources to projects + - Capacity planning for upcoming work + - Resource conflict resolution + - Skills gap analysis --- # Resource Allocation Skill diff --git a/pmo-team/skills/risk-management/SKILL.md b/pmo-team/skills/risk-management/SKILL.md index 4d73fa87..11973eb9 100644 --- a/pmo-team/skills/risk-management/SKILL.md +++ b/pmo-team/skills/risk-management/SKILL.md @@ -1,22 +1,22 @@ --- -name: ring:risk-management +name: risk-management description: | Portfolio-level risk management skill for identifying, assessing, and mitigating risks across multiple projects. Maintains RAID logs and tracks risk responses. - -trigger: | - - Need portfolio risk assessment - - Creating or updating RAID log - - Risk response planning - - Risk correlation analysis - -skip_when: | - - Single project risk → handle in project scope - - Financial risk only → use ring-finops-team - - Technical risk in code → use ring:qa-analyst - -related: - complementary: [portfolio-planning, project-health-check] +metadata: + related: + complementary: + - portfolio-planning + - project-health-check + skip_when: | + - Single project risk → handle in project scope + - Financial risk only → use ring-finops-team + - Technical risk in code → use ring:qa-analyst + trigger: | + - Need portfolio risk assessment + - Creating or updating RAID log + - Risk response planning + - Risk correlation analysis --- # Risk Management Skill diff --git a/pmo-team/skills/using-pmo-team/SKILL.md b/pmo-team/skills/using-pmo-team/SKILL.md index 9c9a580d..3f575223 100644 --- a/pmo-team/skills/using-pmo-team/SKILL.md +++ b/pmo-team/skills/using-pmo-team/SKILL.md @@ -1,24 +1,24 @@ --- -name: ring:using-pmo-team +name: using-pmo-team description: | 6 specialist PMO agents for portfolio management, resource planning, governance, risk analysis, executive reporting, and delivery reporting. Dispatch when you need portfolio-level oversight. - -trigger: | - - Need portfolio-level view across multiple projects - - Resource capacity planning across teams - - Project governance and gate reviews - - Risk management at portfolio level - - Executive reporting and dashboards - -skip_when: | - - Single feature planning → use ring-pm-team - - Code implementation → use ring-dev-team - - Code review → use ring-default reviewers - - Technical writing → use ring-tw-team - -related: - similar: [ring:using-ring, ring:using-pm-team] +metadata: + related: + similar: + - ring:using-ring + - ring:using-pm-team + skip_when: | + - Single feature planning → use ring-pm-team + - Code implementation → use ring-dev-team + - Code review → use ring-default reviewers + - Technical writing → use ring-tw-team + trigger: | + - Need portfolio-level view across multiple projects + - Resource capacity planning across teams + - Project governance and gate reviews + - Risk management at portfolio level + - Executive reporting and dashboards --- # Using Ring PMO Team diff --git a/tw-team/skills/api-field-descriptions/SKILL.md b/tw-team/skills/api-field-descriptions/SKILL.md index 0d065d15..107dedd4 100644 --- a/tw-team/skills/api-field-descriptions/SKILL.md +++ b/tw-team/skills/api-field-descriptions/SKILL.md @@ -1,20 +1,19 @@ --- -name: ring:api-field-descriptions +name: api-field-descriptions description: | Patterns for writing clear, consistent API field descriptions including types, constraints, examples, and edge cases. - -trigger: | - - Writing API field documentation - - Documenting request/response schemas - - Creating data model documentation - -skip_when: | - - Writing conceptual docs → use writing-functional-docs - - Full API endpoint docs → use writing-api-docs - -related: - complementary: [writing-api-docs] +metadata: + related: + complementary: + - writing-api-docs + skip_when: | + - Writing conceptual docs → use writing-functional-docs + - Full API endpoint docs → use writing-api-docs + trigger: | + - Writing API field documentation + - Documenting request/response schemas + - Creating data model documentation --- # API Field Descriptions diff --git a/tw-team/skills/documentation-review/SKILL.md b/tw-team/skills/documentation-review/SKILL.md index 260248e2..631f7daf 100644 --- a/tw-team/skills/documentation-review/SKILL.md +++ b/tw-team/skills/documentation-review/SKILL.md @@ -1,24 +1,25 @@ --- -name: ring:documentation-review +name: documentation-review description: | Comprehensive checklist and process for reviewing documentation quality including voice, tone, structure, completeness, and technical accuracy. - -trigger: | - - Reviewing draft documentation - - Pre-publication quality check - - Documentation audit - - Ensuring style guide compliance - -skip_when: | - - Writing new documentation → use writing-functional-docs or writing-api-docs - - Only checking voice → use voice-and-tone - -sequence: - after: [writing-functional-docs, writing-api-docs] - -related: - complementary: [voice-and-tone, documentation-structure] +metadata: + related: + complementary: + - voice-and-tone + - documentation-structure + sequence: + after: + - writing-functional-docs + - writing-api-docs + skip_when: | + - Writing new documentation → use writing-functional-docs or writing-api-docs + - Only checking voice → use voice-and-tone + trigger: | + - Reviewing draft documentation + - Pre-publication quality check + - Documentation audit + - Ensuring style guide compliance --- # Documentation Review Process diff --git a/tw-team/skills/documentation-structure/SKILL.md b/tw-team/skills/documentation-structure/SKILL.md index c0164a4a..3faca664 100644 --- a/tw-team/skills/documentation-structure/SKILL.md +++ b/tw-team/skills/documentation-structure/SKILL.md @@ -1,21 +1,21 @@ --- -name: ring:documentation-structure +name: documentation-structure description: | Patterns for organizing and structuring documentation including hierarchy, navigation, and information architecture. - -trigger: | - - Planning documentation structure - - Organizing content hierarchy - - Deciding how to split content across pages - - Creating navigation patterns - -skip_when: | - - Writing content → use writing-functional-docs or writing-api-docs - - Checking voice → use voice-and-tone - -related: - complementary: [writing-functional-docs, writing-api-docs] +metadata: + related: + complementary: + - writing-functional-docs + - writing-api-docs + skip_when: | + - Writing content → use writing-functional-docs or writing-api-docs + - Checking voice → use voice-and-tone + trigger: | + - Planning documentation structure + - Organizing content hierarchy + - Deciding how to split content across pages + - Creating navigation patterns --- # Documentation Structure diff --git a/tw-team/skills/using-tw-team/SKILL.md b/tw-team/skills/using-tw-team/SKILL.md index 7e7131da..0a4cd414 100644 --- a/tw-team/skills/using-tw-team/SKILL.md +++ b/tw-team/skills/using-tw-team/SKILL.md @@ -1,23 +1,23 @@ --- -name: ring:using-tw-team +name: using-tw-team description: | Technical writing specialists for functional and API documentation. Dispatch when you need to create guides, conceptual docs, or API references following established documentation standards. - -trigger: | - - Need to write functional documentation (guides, conceptual docs, tutorials) - - Need to write API reference documentation - - Need to review existing documentation quality - - Writing or updating product documentation - -skip_when: | - - Writing code → use dev-team agents - - Writing plans → use pm-team agents - - General code review → use default plugin reviewers - -related: - similar: [ring:using-ring, ring:using-dev-team] +metadata: + related: + similar: + - ring:using-ring + - ring:using-dev-team + skip_when: | + - Writing code → use dev-team agents + - Writing plans → use pm-team agents + - General code review → use default plugin reviewers + trigger: | + - Need to write functional documentation (guides, conceptual docs, tutorials) + - Need to write API reference documentation + - Need to review existing documentation quality + - Writing or updating product documentation --- # Using Ring Technical Writing Specialists diff --git a/tw-team/skills/voice-and-tone/SKILL.md b/tw-team/skills/voice-and-tone/SKILL.md index a48caea8..c42e344c 100644 --- a/tw-team/skills/voice-and-tone/SKILL.md +++ b/tw-team/skills/voice-and-tone/SKILL.md @@ -1,20 +1,21 @@ --- -name: ring:voice-and-tone +name: voice-and-tone description: | Voice and tone guidelines for technical documentation. Ensures consistent, clear, and human writing across all documentation. - -trigger: | - - Need to check voice and tone compliance - - Writing new documentation - - Reviewing existing documentation for style - -skip_when: | - - Only checking structure → use documentation-structure - - Only checking technical accuracy → use docs-reviewer agent - -related: - complementary: [writing-functional-docs, writing-api-docs, documentation-review] +metadata: + related: + complementary: + - writing-functional-docs + - writing-api-docs + - documentation-review + skip_when: | + - Only checking structure → use documentation-structure + - Only checking technical accuracy → use docs-reviewer agent + trigger: | + - Need to check voice and tone compliance + - Writing new documentation + - Reviewing existing documentation for style --- # Voice and Tone Guidelines diff --git a/tw-team/skills/writing-api-docs/SKILL.md b/tw-team/skills/writing-api-docs/SKILL.md index 1c83564b..4654458b 100644 --- a/tw-team/skills/writing-api-docs/SKILL.md +++ b/tw-team/skills/writing-api-docs/SKILL.md @@ -1,26 +1,27 @@ --- -name: ring:writing-api-docs +name: writing-api-docs description: | Patterns and structure for writing API reference documentation including endpoint descriptions, request/response schemas, and error documentation. - -trigger: | - - Documenting REST API endpoints - - Writing request/response examples - - Documenting error codes - - Creating API field descriptions - -skip_when: | - - Writing conceptual guides → use writing-functional-docs - - Reviewing documentation → use documentation-review - - Writing code → use dev-team agents - -sequence: - before: [documentation-review] - -related: - similar: [writing-functional-docs] - complementary: [api-field-descriptions, documentation-structure] +metadata: + related: + similar: + - writing-functional-docs + complementary: + - api-field-descriptions + - documentation-structure + sequence: + before: + - documentation-review + skip_when: | + - Writing conceptual guides → use writing-functional-docs + - Reviewing documentation → use documentation-review + - Writing code → use dev-team agents + trigger: | + - Documenting REST API endpoints + - Writing request/response examples + - Documenting error codes + - Creating API field descriptions --- # Writing API Reference Documentation diff --git a/tw-team/skills/writing-functional-docs/SKILL.md b/tw-team/skills/writing-functional-docs/SKILL.md index 46f8a68d..199c28ec 100644 --- a/tw-team/skills/writing-functional-docs/SKILL.md +++ b/tw-team/skills/writing-functional-docs/SKILL.md @@ -1,26 +1,27 @@ --- -name: ring:writing-functional-docs +name: writing-functional-docs description: | Patterns and structure for writing functional documentation including guides, conceptual explanations, tutorials, and best practices documentation. - -trigger: | - - Writing a new guide or tutorial - - Creating conceptual documentation - - Documenting best practices - - Writing "how to" content - -skip_when: | - - Writing API reference → use writing-api-docs - - Reviewing documentation → use documentation-review - - Writing code → use dev-team agents - -sequence: - before: [documentation-review] - -related: - similar: [writing-api-docs] - complementary: [voice-and-tone, documentation-structure] +metadata: + related: + similar: + - writing-api-docs + complementary: + - voice-and-tone + - documentation-structure + sequence: + before: + - documentation-review + skip_when: | + - Writing API reference → use writing-api-docs + - Reviewing documentation → use documentation-review + - Writing code → use dev-team agents + trigger: | + - Writing a new guide or tutorial + - Creating conceptual documentation + - Documenting best practices + - Writing "how to" content --- # Writing Functional Documentation