dev-workflow

Purpose

This skill is the default operating procedure for implementing changes in this repository.

It turns a request into an implementable plan with verifiable outcomes:

requirements → design → test design → implementation → verification → final gate.

When to use

Use this skill for any task that changes code and/or tests. It is mandatory.

How to use

1. •

   Open references/dev-workflow.md and follow it step-by-step.

2. •

   Write the Change Brief and the Requirements (EARS “shall” + acceptance criteria).

1.5) If runtime behavior changes, add an Observability Plan (logs/metrics/traces) and invoke $observability when unsure.

1.75) If the change is structural (new modules, boundary changes, refactors across layers), invoke $code-smells-and-antipatterns.

1. •

   Create a Test List (3–10). Decide whether to proceed with TDD.

   • •If doing TDD, explicitly invoke $test-driven-development.
2. •

   Legacy check (mandatory): if tests are missing or behavior is nondeterministic, explicitly invoke $working-with-legacy-code before refactoring.

3. •

   C++ header gate (mandatory): if .hpp / .h is in scope, explicitly invoke $code-readability and apply the mandatory Doxygen rules.

4. •

   Implementation:

   • •For readability: invoke $code-readability when you need concrete guidance.
   • •For modularity / coupling / boundaries: invoke $modularity.
   • •For Clean Architecture boundaries: invoke $architecture-boundaries.
   • •For error paths: invoke $error-handling.
   • •For NFRs: invoke $nfr-iso25010 when relevant.
   • •If requirements docs must be updated: invoke $requirements-documentation.
5. •

   Verification: run the repo’s canonical commands for build / format / static analysis / tests until green.

6. •

   Before submitting, explicitly invoke $quality-gate and keep fixing until it reports 0 findings.

Output expectation

• •Your final output must follow AGENTS.md “Required final output”.
• •Any skipped checks must include a reason and a reproducible procedure.