qmu

Owns logical validity — type-driven design, functional style, layer segregation, data persistence strategy, and the testing strategy that covers what types cannot express.

testing1

report

Story writing, PR creation, and release readiness assessment for branch reporting.

business1

select-scan-agents

Select scanner agents based on scan mode and branch changes.

data-ai1

validate-writer-output

Validate that writer subagent output files exist and are non-empty before proceeding to index updates.

testing1

write-release-note

Release note content structure and guidelines for GitHub Releases.

documentation1

gather-git-context

Gather git context and branch data in one call.

data-ai1

reliability-lead

Owns infrastructure provisioning, environment portability, disaster recovery, and operational resilience for the project.

devops1

manage-quality

Owns quality standards, assurance processes, and continuous improvement practices for the project.

testing1

plugins/standards/skills/review-sections

# Review Sections Guidelines for generating story sections 4-8 (Outcome, Historical Analysis, Concerns, Ideas, Successful Development Patterns) from archived tickets. ## Input - Branch name - List of archived ticket paths ## Analysis Process 1. **Read all archived tickets** for the branch using Glob pattern 2. **Extract relevant content** from each ticket: - Overview section for accomplishments - Related History section for patterns - Considerations section for concerns and ideas

tools1

write-overview

Content guidelines for generating overview, highlights, motivation, and journey sections.

documentation1

drive

Implementation workflow, approval flow, final report, archive, and frontmatter update for drive sessions.

business1

write-changelog

Generate changelog entries from archived tickets and update CHANGELOG.md.

documentation1

availability-lead

Owns CI/CD pipelines, infrastructure provisioning, environment portability, observability, disaster recovery, and operational resilience for the project.

testing1

accessibility-lead

Owns user experience design, interaction patterns, user journeys, and onboarding paths for the project.

content-media1

write-release-note

Release note content structure and guidelines for GitHub Releases.

documentation1

review-sections

Generate branch-story sections 4-7 (Outcome, Historical Analysis, Concerns, Successful Development Patterns) from archived tickets and carry-over verdicts. Used by the report workflow when assembling a PR story.

development1

validate-writer-output

Validate that writer subagent output files exist and are non-empty before proceeding to index updates.

testing1

gather

Gather git context and ticket metadata in single calls.

data-ai1

trip-protocol

Two-phase collaborative workflow protocol and artifact conventions.

tools1

db-lead

Owns data formats, frontmatter schemas, file naming conventions, and data validation for the project's persistency layer.

development1

analyze-policy

Generic framework for policy-based repository analysis. Provides output templates, inference guidelines, and context gathering scripts.

development1

analyze-viewpoint

Generic framework for viewpoint-based architecture analysis. Provides output templates, assumption rules, and context gathering scripts.

development1

quality-lead

Owns code quality standards, linting rules, review processes, testing strategy, coverage targets, and metrics used to maintain correctness and maintainability for the project.

development1

delivery-lead

Owns the CI/CD pipeline stages, deployment strategies, and artifact promotion flow from source to production for the project.

testing1

observability-lead

Owns the observability strategy including metrics collection, logging practices, tracing implementation, and alerting thresholds for the project.

testing1

ux-lead

Owns user experience design, interaction patterns, user journeys, and onboarding paths for the project.

content-media1

managers-principle

Cross-cutting principles that apply to all manager sub-agents.

testing1

write-spec

Spec document structure, formatting rules, and guidelines for updating .workaholic/specs/.

development1

write-terms

Term document structure, formatting rules, and guidelines for updating .workaholic/terms/.

development1

discover

Guidelines for discovering historical context, source code, and repository standards.

development1

manage-architecture

Owns software experience definition, system structure, and component taxonomy from infrastructure to application layer.

devops1

manage-project

Owns business context, stakeholder relationships, timeline, issues, and solutions for the project.

tools1

leading-validity

Owns logical validity — type-driven design, functional style, layer segregation, data persistence strategy, and the testing strategy that covers what types cannot express.

testing1

write-release-note

Release note content structure and guidelines for GitHub Releases.

documentation1

review-sections

development1

leading-security

Owns the assets worth protecting, threat model, authentication/authorization boundaries, and safeguards for the project.

testing1

trip-protocol

Two-phase collaborative workflow protocol and artifact conventions.

tools1

leading-availability

Owns CI/CD pipelines, infrastructure provisioning, environment portability, observability, disaster recovery, and operational resilience for the project.

testing1