@elvis1513/auto-coding-skill 4.0.0 → 4.1.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,29 +1,119 @@
1
- <!-- auto-coding-skill:managed-agents:start version=4.0.0 -->
2
-
3
- Follow `docs/ENGINEERING.md` for project facts, risk rules, and validation routes.
4
- Use the delivery-first flow: analyze, decompose, design only when needed, develop,
5
- run one final changed-scope gate, then commit and push. Push ends coding; do not
6
- wait for Jenkins, deployment, or owner acceptance unless the user opens a
7
- diagnostic task.
8
-
9
- Before writing, inspect the checkout. A clean single-writer task stays on the
10
- current branch. Pre-existing unrelated changes or multiple writers require one
11
- isolated worktree per writer with non-overlapping owned paths. If no diff is
12
- produced, do not commit or push and do not create a temporary branch. Never
13
- restore, reset, stash, clean, or overwrite unknown changes.
14
-
15
- Delegate only when independent work has a clear benefit. Ordinary tasks default
16
- to the main agent. Require fingerprinted review for high-risk, cross-module,
17
- parallel, or explicitly configured work. The main agent owns the final gate,
18
- commit, push, ordered integration, and cleanup.
19
-
20
- Run all matching `validation.routes` commands once in stable order. Unmapped code
21
- must fail; docs-only changes may use the built-in diff check. Focused tests may be
22
- rerun during development, but do not repeat expensive full gates. Do not create
23
- taskbook, closure, evidence, or design documents unless the task genuinely needs
24
- a durable artifact.
25
-
26
- Use configured `access.*` values when needed. Plaintext credentials are allowed;
27
- do not invent or echo them unnecessarily.
1
+ <!-- auto-coding-skill:managed-agents:start version=4.1.1 -->
2
+ # Shared Engineering Protocol
3
+
4
+ This file is fully managed by `auto-coding-skill`. Keep project-specific facts,
5
+ access values, risk rules, and validation routes in `docs/ENGINEERING.md`.
6
+
7
+ ## Authority
8
+
9
+ Use this order when sources disagree:
10
+
11
+ 1. The current user request.
12
+ 2. Code, tests, schemas, migrations, and runtime configuration for behavior that
13
+ exists now.
14
+ 3. `docs/ENGINEERING.md` for project facts and workflow configuration.
15
+ 4. Current interface documentation for intended contracts.
16
+ 5. Accepted DD/ADR for lasting decisions.
17
+ 6. Taskbooks, closures, reviews, and deployment records as history only.
18
+
19
+ Update authoritative documentation when a change intentionally changes its
20
+ contract. Never let stale history override current implementation.
21
+
22
+ ## Minimum mechanism budget
23
+
24
+ Use only mechanisms that improve expected delivery speed or defect prevention.
25
+ The default budget is:
26
+
27
+ | Situation | Required mechanisms |
28
+ | --- | --- |
29
+ | Read-only question | none |
30
+ | Obvious clean serial edit | analysis, affected gate, commit/push |
31
+ | Terminal ledger/archive maintenance | targeted consistency check, one commit |
32
+ | Dirty checkout or concurrent writer | registered lifecycle and isolated worktree |
33
+ | High-risk or contract-crossing change | necessary design and independent review |
34
+ | Multiple independent writers | one task/worktree/lease per writer, ordered integration |
35
+
36
+ Do not add classify, task lifecycle, durable design, subagents, reviewer, or a
37
+ worktree outside this budget merely because the tool exists. If impact is unclear,
38
+ run `classify` and follow `mechanism_plan.required`; items in
39
+ `mechanism_plan.not_required` stay off unless the user explicitly requests them.
40
+
41
+ Normal delivery is:
42
+
43
+ `analysis → decomposition → necessary design → development → one bounded final
44
+ changed-scope gate → commit/push`.
45
+
46
+ Push to the target branch ends normal coding. Do not poll Jenkins, deploy, or run
47
+ owner acceptance automatically. A user-requested diagnosis of the just-pushed
48
+ failure may continue in the same conversation/task without a second lifecycle.
49
+
50
+ ## Git and parallel work
51
+
52
+ - One writer in a clean checkout works directly on the current branch without a
53
+ task lifecycle.
54
+ - Existing unrelated changes, another writer, or configured mandatory isolation
55
+ requires a registered task branch/worktree.
56
+ - Every writing agent owns a distinct task ID, worktree, writer lease,
57
+ non-overlapping `owned_paths`, and prerequisite commit SHAs.
58
+ - Never let multiple writing agents share a checkout. Never restore, reset, stash,
59
+ clean, overwrite, or commit unknown changes.
60
+ - No diff means no commit, push, or temporary branch.
61
+ - The main agent integrates in dependency order and removes only clean, safely
62
+ merged temporary worktrees and branches.
63
+ - Do not sync or upgrade while any registered task is active.
64
+
65
+ ## Design, agents, and review
66
+
67
+ - Micro and standard tasks stay main-agent-only unless independent delegation has
68
+ a concrete latency or expertise benefit.
69
+ - Create DD/ADR only for lasting cross-module, API, data, security, deployment,
70
+ or key user-flow decisions.
71
+ - Use read-only explorer/docs/browser agents only for independent questions.
72
+ - Use parallel fixers only for bounded, dependency-free, non-overlapping units.
73
+ - Require fingerprinted review only for high-risk, contract-crossing, parallel,
74
+ or explicitly configured work.
75
+ - Review blocks only defects introduced or worsened in the promised scope.
76
+ Adjacent existing issues are non-blocking follow-ups.
77
+ - Semantic changes invalidate approval. Mechanical documentation-only corrections
78
+ may receive a targeted recheck by the same reviewer.
79
+ - Historical debt does not block ordinary delivery; block only new or worsened
80
+ P0/P1 issues.
81
+
82
+ ## Bounded real validation
83
+
84
+ - `risk.rules` controls reasoning/review depth. `validation.routes` alone selects
85
+ executable closure checks.
86
+ - Every changed code/config path must match one or more explicit routes. Run every
87
+ matched command once in stable order and de-duplicate references.
88
+ - Unmapped code or blank commands fail before staging. Documentation-only work may
89
+ use the built-in diff/format check. `git diff --check` is hygiene, not business
90
+ validation.
91
+ - Focused tests may run and rerun during development. Run one final routed gate
92
+ after the diff is stable.
93
+ - The final gate has hard project-configurable ceilings of 120 seconds per command
94
+ and 180 seconds total. A timeout must narrow the route; never expand or retry it
95
+ as a full gate.
96
+ - Do not proactively install dependencies. Only after the selected route fails
97
+ because a repository-locked dependency is absent may it be restored once and
98
+ only that route retried.
99
+ - Full regression, repository-wide scans, builds, Docker, Jenkins, deployment,
100
+ live-device writes, browser/API acceptance, and target checks are explicit
101
+ diagnostics, not normal closure.
102
+ - External-system writes require the project safety rule or user confirmation;
103
+ use fixtures/simulators when the project supplies them.
104
+
105
+ ## Documentation and access
106
+
107
+ - This AGENTS file is the single behavioral protocol. The installed `SKILL.md`
108
+ contains invocation guidance. `docs/ENGINEERING.md` is the single project
109
+ configuration and facts source. Do not repeat the protocol elsewhere.
110
+ - Put larger product, repository, and runtime facts under `docs/project/` and link
111
+ them from ENGINEERING.
112
+ - Ordinary work creates no taskbook, closure Markdown, evidence JSONL, active-task
113
+ document, or design file. Machine coordination/evidence stays in Git
114
+ common/local state and cannot change the reviewed diff.
115
+ - Pure ledger/archive reconciliation is terminal: validate, commit once, and stop.
116
+ - Fill configured project/Jenkins/GitLab/Nexus access fields during initialization.
117
+ Plaintext values are allowed; do not invent or unnecessarily echo credentials.
28
118
 
29
119
  <!-- auto-coding-skill:managed-agents:end -->