standards

Owns accessibility compliance, i18n support, assistive technology considerations, and inclusive design policy for the project.

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

Update root CHANGELOG.md from archived tickets. Groups entries by category and links to commits and tickets.

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

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

Owns external dependencies, file system layout, installation procedures, and environment requirements for the project.

Analyze repository from model viewpoint and generate spec documentation.

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

Generate overview content for story by analyzing commit history.

Evaluate decision-making quality across five viewpoints

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

Owns code quality standards, linting rules, review processes, and metrics used to maintain maintainability for the project.

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

Owns data backup schedules, retention policies, disaster recovery procedures, and RTO/RPO targets for the project.

Generate release notes from branch story for GitHub Releases.

Generate story sections 5-8 (Outcome, Historical Analysis, Concerns, Ideas) by analyzing archived tickets.

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

Update .workaholic/terms/ documentation to maintain consistent term definitions. Use after completing implementation work.

Owns verification and validation strategy, testing levels, coverage targets, and processes that ensure correctness for the project.

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

Evaluation framework for analyzing decision-making quality across five dimensions.

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

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

Owns accessibility compliance, i18n support, assistive technology considerations, and inclusive design policy for the project.

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

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

Owns external dependencies, file system layout, installation procedures, and environment requirements for the project.

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

Owns code quality standards, linting rules, review processes, and metrics used to maintain maintainability for the project.

Owns data backup schedules, retention policies, disaster recovery procedures, and RTO/RPO targets for the project.

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

Owns verification and validation strategy, testing levels, coverage targets, and processes that ensure correctness for the project.

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

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

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

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

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

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

Guidelines for generating story sections 5-8 (Outcome, Historical Analysis, Concerns, Ideas) from archived tickets.

Select scanner agents based on scan mode and branch changes.

Translation policies for converting English markdown files to other languages (primarily Japanese). Use when translating documentation or README files.

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

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

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

Release note content structure and guidelines for GitHub Releases.

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

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