dso

Plugin dso from marketplace digital-service-orchestra in navapbc/digital-service-orchestra. Commands read from the repo's manifest — 1 month ago.

Skills (31)

• architect-foundation

  Deep-dive architectural scaffolding for an existing project — reads .claude/project-understanding.md (written by /dso:onboarding), uses Socratic dialogue to uncover enforcement preferences and anti-pattern risks, and generates targeted enforcement scaffolding without re-running project detection.

• brainstorm

  Use when starting a new feature or epic — turns an idea into a defined, ticket-ready epic through Socratic dialogue, approach design, and milestone spec creation.

• create-bug

  Guidance for creating well-formatted, evidence-based bug reports using the shared bug report template and ticket CLI.

• debug-everything

  Diagnose and fix all outstanding bugs (validation failures AND open ticket bugs), test failures, lint errors, and infrastructure issues using orchestrated sub-agents with TDD discipline

• design-review

  Use when reviewing proposed designs (code, wireframes, screenshots) against an established .claude/design-notes.md, or when enforcing design system compliance before merging UI changes

• dryrun

  Use when the user wants to preview what a skill would do without making changes to tickets, the file system, or git

• end-session

  End Session - Worktree Cleanup and Task Summary

• fix-bug

  Classify bugs by type and severity, then route through the appropriate investigation and fix path.

• fix-cascade-recovery

  Emergency brake for runaway cascades. Stops edits, assesses damage, decides revert, then hands off to /dso:fix-bug for investigation.

• generate-claude-md

  Generate a project-specific CLAUDE.md file from workflow-config.yaml and the Digital Service Orchestra template

• implementation-plan

  Use when a user story or simple epic needs to be broken into atomic, TDD-driven implementation tasks with architectural review, or when planning how to implement a specific ticket item

• init

  Initialize project with Digital Service Orchestra config

• interface-contracts

  Interface contract design for parallel agent development

• onboarding

  Use when starting a new project or joining an existing one — conducts a Socratic dialogue to build a shared understanding of the project's stack, commands, architecture, infrastructure, CI pipeline, design system, and enforcement preferences.

• oscillation-check

  Detect feedback oscillation in iterative review loops using structural diff comparison. Invoke before implementing review feedback.

• plan-review

  Orchestrator-level skill that reviews plans and designs before user approval by dispatching a dso:plan-review sub-agent. Invoke before presenting any plan or design to the user, or before calling ExitPlanMode. Do NOT dispatch this skill itself as a sub-agent — it requires the Agent tool and will ref

• playwright-debug

  Use when debugging a UI or browser-visible bug. Enforces a 3-tier hypothesis-first process that minimizes @playwright/cli token usage by exhausting static code analysis and targeted JS evidence before escalating to full browser interaction.

• preplanning

  Use when decomposing a ticket epic into prioritized user stories with measurable done definitions, or when auditing and reconciling existing epic children before implementation

• quick-ref

  Auto-discover and display all plugin scripts and skills available in this workflow plugin.

• resolve-conflicts

  Agent-assisted git merge/rebase conflict resolution with confidence-gated automation

• retro

  Use when performing periodic project health reviews, optimizing development workflow, cleaning up worktrees, auditing test quality, or identifying technical debt and maintenance needs

• review-protocol

  Use when a skill needs structured multi-perspective review with conflict detection, revision cycles, and standardized JSON output — replaces ad-hoc mental reviews and custom sub-agent review logic

• review-stats

  Display review event statistics — shows reviewer tier distribution, resolution rates, and trends over time.

• roadmap

  Use when the user wants to transform a high-level product vision, PRD, or project idea into a prioritized roadmap of epics, or when they want to brainstorm and architect project milestones

• sprint

  Execute Epic - Multi-Agent Orchestration

• tickets-health

  Issue health validation and remediation

• ui-discover

  Generates or refreshes the UI Discovery Cache for a project. Inventories components via Glob/Grep, crawls routes via Playwright, and writes structured results to .ui-discovery-cache/. Produces a deterministic validation script for git-based cache invalidation. Run once before starting an epic's wire

• update-docs

  Invoke the doc-writer agent to update project documentation based on recent changes. Scoped to a commit range (default main...HEAD). Use after an epic completes or when documentation is out of sync.

• using-dso

  Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

• validate-work

  Use when verifying project health after completing work, before closing tasks, or when you need confidence that code, CI, staging deployment, and live environment are all passing. Does not fix issues — only detects and reports them.

• verification-before-completion

  Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Slash commands (3)

• /dso:commit
• /dso:end
• /dso:review

Subagents (40)

• approach-decision-maker

  Evaluates implementation proposals against 5 quality dimensions and returns ADR-style selection rationale or counter-proposal

• bloat-blue-team

  Evaluates probabilistic bloat candidates from /dso:remediate, classifying each as CONFIRM (likely bloat), DISMISS (false positive), or NEEDS_HUMAN (ambiguous). Enforces asymmetric error policy — defaults to DISMISS when uncertain because false CONFIRMs are amplified downstream.

• bloat-resolver

  Applies confirmed bloat removals from /dso:remediate Path B (auto-resolve). Treats its output as final — performs dependency checks before each deletion and emits NO_CHANGE with categorized reasons when removal is unsafe.

• blue-team-filter

  Structured filter that evaluates red team adversarial findings against the original story map and removes false positives, speculative concerns, and low-signal noise.

• bot-psychologist

  LLM behavioral debugger agent. Diagnoses divergent, unpredictable, or failing behavior in other LLMs and agents using a 16-point failure taxonomy, 5 RCA probes, and an iterative hypothesis-experiment-analyze loop. Emits a structured RESULT schema compatible with /dso:fix-bug.

• code-reviewer-deep-arch

  Deep-tier architectural reviewer (Opus): synthesizes specialist findings, assesses systemic risk, produces unified verdict across all dimensions.

• code-reviewer-deep-correctness

  Deep-tier correctness specialist (Sonnet A): focused exclusively on correctness — edge cases, error handling, security, efficiency.

• code-reviewer-deep-hygiene

  Deep-tier hygiene/design specialist (Sonnet C): focused on hygiene, design, and maintainability.

• code-reviewer-deep-verification

  Deep-tier verification specialist (Sonnet B): focused exclusively on verification — test presence, quality, edge case coverage, mock correctness.

• code-reviewer-light

  Light-tier code reviewer: single-pass, highest-signal checklist for fast feedback on low-to-medium-risk changes.

• code-reviewer-performance

  Performance reviewer (Opus): calibrated performance analysis with bright-line severity rules for scaling failures and resource exhaustion.

• code-reviewer-security-blue-team

  Security blue team reviewer (Opus): context-aware triage of red team findings with dismiss/downgrade/sustain authority.

• code-reviewer-security-red-team

  Security red team reviewer (Opus): aggressive security detection without ticket context for AI-advantaged security concerns.

• code-reviewer-standard

  Standard-tier code reviewer: comprehensive review across all five scoring dimensions for moderate-to-high-risk changes.

• code-reviewer-test-quality

  Test quality reviewer (Opus): detects test bloat patterns including change-detector tests, implementation-coupled assertions, tautological tests, source-file-grepping, and existence-only assertions.

• completion-verifier

  Independently verifies that success criteria (SC) for epics and done definitions (DD) for stories are met by the implementation before closure is approved.

• complexity-evaluator

  Classifies a ticket as TRIVIAL/MODERATE/COMPLEX (or SIMPLE/MODERATE/COMPLEX for epics) using an 8-dimension rubric.

• conflict-analyzer

  Analyzes git merge conflicts, classifies each conflicted file, and proposes a resolution with confidence scoring.

• cross-epic-interaction-classifier

  Classifies interactions between a new epic and open/in-progress epics, detecting shared-resource overlaps with four-tier severity classification (benign, consideration, ambiguity, conflict).

• doc-writer

  Documentation optimization agent that enforces a 4-tier schema and decision engine to keep project docs accurate and lean after epic completion.

• feasibility-reviewer

  Verifies external tool feasibility during brainstorm by searching for evidence of real, working integrations before implementation begins.

• huge-diff-refactor-anomaly

  Opus reviewer dispatched during the large-refactor confirmed-refactor branch. Receives concatenated diffs of files flagged as anomalous by the haiku conformance sweep. Reports pattern_conformance, behavioral_drift, and callsite_completeness findings using the standard 5-dimension reviewer schema.

• huge-diff-reviewer-light

  Opus-model fallback reviewer for the light tier, used when the large-refactor review path activates and the diff exceeds the huge_diff_file_threshold. Identical behavior to code-reviewer-light but always runs on opus.

• huge-diff-reviewer-standard

  Opus-model fallback reviewer for the standard tier, used when the large-refactor review path activates and the diff exceeds the huge_diff_file_threshold. Identical behavior to code-reviewer-standard but always runs on opus.

• intent-search

  Pre-investigation gate agent (Intent Gate) for /dso:fix-bug. Searches closed/archived tickets, git history, ADRs, design docs, and code comments to determine whether a bug aligns with or contradicts the system's documented intent.

• investigator-advanced-code-tracer

  Bug investigator (opus, ADVANCED Code Tracer lens): execution path tracing, intermediate variable tracking, code-evidence hypothesis set.

• investigator-advanced-historical

  Bug investigator (opus, ADVANCED Historical lens): timeline reconstruction, fault tree analysis, git bisect, change-history hypothesis set.

• investigator-basic

  Bug investigator (sonnet, BASIC tier): single-pass localization, five whys, single proposed fix for low-complexity bugs.

• investigator-escalated-code-tracer

  Bug investigator (opus, ESCALATED Code Tracer): deep execution-path tracing, dependency-ordered analysis, state and concurrency inspection.

• investigator-escalated-empirical

  Bug investigator (opus, ESCALATED Empirical Agent): authorized to add temporary logging/debugging; veto authority over theoretical consensus; must confirm artifact revert.

• investigator-escalated-history

  Bug investigator (opus, ESCALATED History Analyst): deep timeline reconstruction, fault tree, commit bisection beyond ADVANCED depth.

• investigator-escalated-web

  Bug investigator (opus, ESCALATED Web Researcher): error pattern analysis, dependency changelogs, upstream issue correlation; WebSearch/WebFetch authorized.

• investigator-intermediate-fallback

  Bug investigator (opus, INTERMEDIATE fallback persona): same investigation depth as intermediate when error-detective is unavailable.

• investigator-intermediate

  Bug investigator (opus, INTERMEDIATE tier): dependency-ordered reading, intermediate variable tracking, hypothesis elimination, ≥2 ranked fixes with tradeoffs.

• plan-review

  Plan and design reviewer agent. Evaluates implementation plans and design artifacts on feasibility, completeness, YAGNI, and codebase alignment before the user sees them. Dispatched by the /dso:plan-review skill. Use subagent_type "dso:plan-review" to dispatch this agent.

• red-team-reviewer

  Adversarial reviewer that attacks preplanning story maps for cross-story blind spots, implicit assumptions, and interaction gaps across 7 taxonomy categories.

• red-test-evaluator

  Triages RED test writer failures with REVISE/REJECT/CONFIRM verdicts. Aligned with shared behavioral testing standard.

• red-test-writer

  Writes behavioral RED tests for TDD workflows, rejecting change-detector patterns.

• scope-drift-reviewer

  Post-fix scope-drift classifier for /dso:fix-bug. Reviews a completed fix against the original ticket scope to detect whether the diff introduces behavioral changes outside the ticket boundary. Emits a GATE_SIGNAL conforming to gate-signal-schema.md.

• ui-designer

  Creates design artifacts for a story ID. Produces a Design Brief (Lite track) or full Design Manifest (spatial layout tree, SVG blueprint, token overlay, manifest). Returns structured payload conforming to docs/contracts/ui-designer-payload.md.

Hooks (14)

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh dispatchers/session-start.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh dispatchers/pre-bash.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh dispatchers/pre-edit.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh dispatchers/pre-write.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh dispatchers/pre-enterplanmode.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh dispatchers/pre-exitplanmode.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh dispatchers/pre-taskoutput.sh

• PostToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh dispatchers/post-bash.sh

• PostToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh dispatchers/post-edit.sh

• PostToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh dispatchers/post-write.sh

• PostToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh dispatchers/post-agent.sh

• Stop

  ${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh dispatchers/stop.sh

• PostToolUseFailure

  ${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh dispatchers/post-failure.sh

• UserPromptSubmit

  ${CLAUDE_PLUGIN_ROOT}/hooks/run-hook.sh fix-bug-skill-directive.sh