AgentSkillsCN

dev-workflow

任何代码或测试变更都必须严格遵循端到端工作流程：需求 → 设计 → 测试清单/TDD → 实现 → 验证（构建/格式化/静态分析/测试）→ 质量门。自始至终贯彻代码可读性、模块化、架构边界以及错误处理等核心原则。

SKILL.md
--- frontmatter
name: dev-workflow
description: "MANDATORY end-to-end workflow for any code/test change: requirements → design → test list/TDD → implement → verify (build/format/static-analysis/tests) → quality gate. Enforces code-readability, modularity, architecture-boundaries, and error-handling from the start."
metadata:
  short-description: End-to-end 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.5) Concurrency & Performance check (mandatory):

  • •If concurrency/parallelism is introduced or changed: invoke $concurrency-core and $thread-safety-tooling.
  • •If ROS2 code is affected: also invoke $concurrency-ros2.
  • •If Android code is affected: also invoke $concurrency-android.
  • •If runtime behavior changes: invoke $observability.
  • •If performance targets are part of the goal: invoke $nfr-iso25010.
  1. •

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

  2. •

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

  3. •

    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.
  4. •

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

  5. •

    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.