@elvis1513/auto-coding-skill 3.0.4 → 4.1.0
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.
- package/README.md +159 -328
- package/cli/assets/agents/explorer.toml +1 -1
- package/cli/assets/agents/fixer.toml +4 -4
- package/cli/assets/agents/reviewer.toml +12 -12
- package/cli/assets/skill/SKILL.md +135 -234
- package/cli/assets/skill/data/policies/workflow-migrations-v1.json +291 -5
- package/cli/assets/skill/data/templates/ENGINEERING.md +164 -292
- package/cli/assets/skill/data/templates/bridges/AGENTS.md +133 -14
- package/cli/assets/skill/scripts/ap.py +884 -221
- package/cli/assets/skill/scripts/scaffold_templates.py +40 -5
- package/cli/src/index.js +180 -93
- package/cli/tests/ap_concurrency_test.py +109 -24
- package/cli/tests/ap_profiles_test.py +81 -41
- package/cli/tests/index.test.js +114 -77
- package/package.json +2 -2
- package/cli/assets/skill/data/templates/docs/tasks/closure-log.md +0 -17
- package/cli/assets/skill/data/templates/docs/tasks/taskbook.md +0 -30
|
@@ -1,5 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
workflow:
|
|
3
|
+
skill_version: "4.1.0"
|
|
3
4
|
mode: "dev"
|
|
4
5
|
profile: "auto"
|
|
5
6
|
completion: "push"
|
|
@@ -49,337 +50,208 @@ concurrency:
|
|
|
49
50
|
disposable_ignored: []
|
|
50
51
|
|
|
51
52
|
commands:
|
|
52
|
-
|
|
53
|
-
|
|
54
|
-
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
|
|
53
|
+
# Optional convenience command. Projects may instead define only the named
|
|
54
|
+
# commands referenced by validation.routes. `autocoding sync` fills this only
|
|
55
|
+
# when package.json declares `test:changed`.
|
|
56
|
+
project_fast: ""
|
|
57
|
+
|
|
58
|
+
validation:
|
|
59
|
+
on_unmapped: "error"
|
|
60
|
+
# Initialization must replace this with explicit project path-to-command
|
|
61
|
+
# mappings. An empty list is intentionally fail-closed for code changes.
|
|
62
|
+
routes: []
|
|
63
|
+
|
|
64
|
+
risk:
|
|
60
65
|
rules: []
|
|
61
66
|
|
|
62
67
|
structure:
|
|
63
68
|
enabled: true
|
|
64
69
|
enforcement: "advisory"
|
|
65
70
|
architecture_standard: "project-defined"
|
|
66
|
-
max_file_lines_warn: 800
|
|
67
|
-
max_file_lines_block: 1500
|
|
68
|
-
max_function_lines_warn: 120
|
|
69
|
-
max_added_lines_to_large_file: 80
|
|
70
|
-
require_reuse_search: true
|
|
71
|
-
block_new_responsibility_in_large_file: true
|
|
72
|
-
allow_large_files:
|
|
73
|
-
- ".agents/skills/**"
|
|
74
|
-
- "docs/tools/autopipeline/**"
|
|
75
|
-
- "generated/**"
|
|
76
|
-
- "**/generated/**"
|
|
77
|
-
- "vendor/**"
|
|
78
|
-
- "dist/**"
|
|
79
|
-
- "build/**"
|
|
80
|
-
- "target/**"
|
|
81
|
-
- "node_modules/**"
|
|
82
|
-
- "**/*.generated.*"
|
|
83
|
-
- "**/*.min.js"
|
|
84
|
-
- "**/*.map"
|
|
85
71
|
accepted_debt_paths: []
|
|
86
72
|
layer_rules:
|
|
87
73
|
enabled: true
|
|
88
74
|
block: false
|
|
89
75
|
|
|
90
76
|
optimization:
|
|
91
|
-
completion_policy: "
|
|
77
|
+
completion_policy: "no-new-debt"
|
|
92
78
|
require_baseline_for_global_review: false
|
|
93
79
|
report_accepted_debt_as_findings: false
|
|
94
80
|
|
|
95
81
|
docs:
|
|
96
|
-
|
|
97
|
-
closure_log: "docs/tasks/closure-log.md"
|
|
98
|
-
evidence_log: "docs/tasks/evidence.jsonl"
|
|
99
|
-
active_task_dir: "docs/tasks/active"
|
|
100
|
-
task_closure_dir: "docs/tasks/closures"
|
|
101
|
-
task_evidence_dir: "docs/tasks/evidence"
|
|
82
|
+
framework: "engineering-centered"
|
|
102
83
|
design_dir: "docs/design"
|
|
103
|
-
task_archive_dir: "docs/tasks/archives"
|
|
104
|
-
design_archive_dir: "docs/archive/design"
|
|
105
|
-
archive_index: "docs/tasks/archive-index.md"
|
|
106
|
-
ledger_check_enabled: true
|
|
107
|
-
ledger_block_on_exceed: true
|
|
108
|
-
active_taskbook_max_lines: 1200
|
|
109
|
-
active_closure_log_max_lines: 800
|
|
110
|
-
active_design_max_files: 120
|
|
111
84
|
health_baseline: "docs/reviews/project-health-baseline.md"
|
|
112
85
|
optimization_backlog: "docs/reviews/optimization-backlog.md"
|
|
113
86
|
structure_standard: "docs/architecture/structure-standard.md"
|
|
114
87
|
api_docs_required: false
|
|
115
88
|
api_doc: "docs/interfaces/api.md"
|
|
116
89
|
api_change_log: "docs/interfaces/api-change-log.md"
|
|
117
|
-
regression_matrix: "docs/testing/regression-matrix.md"
|
|
118
|
-
bug_list: "docs/bugs/bug-list.md"
|
|
119
|
-
summary_dir: "docs/tasks/summaries"
|
|
120
90
|
---
|
|
121
91
|
|
|
122
92
|
# Engineering Workflow
|
|
123
93
|
|
|
124
|
-
<!-- auto-coding-skill:managed-workflow:start version=
|
|
125
|
-
|
|
126
|
-
This file
|
|
127
|
-
|
|
128
|
-
|
|
129
|
-
|
|
130
|
-
|
|
131
|
-
|
|
132
|
-
|
|
133
|
-
|
|
134
|
-
|
|
135
|
-
|
|
136
|
-
|
|
137
|
-
|
|
138
|
-
|
|
139
|
-
|
|
140
|
-
|
|
141
|
-
|
|
142
|
-
|
|
143
|
-
|
|
144
|
-
|
|
145
|
-
|
|
146
|
-
|
|
147
|
-
|
|
148
|
-
|
|
149
|
-
|
|
150
|
-
|
|
151
|
-
|
|
152
|
-
|
|
153
|
-
|
|
154
|
-
|
|
155
|
-
|
|
156
|
-
|
|
157
|
-
|
|
158
|
-
|
|
159
|
-
- `project.name`
|
|
160
|
-
- all URL, username, and direct password fields under `access.project`,
|
|
161
|
-
`access.jenkins`, `access.gitlab`, and `access.nexus`; blank/TODO values make
|
|
162
|
-
initialization incomplete and block `doctor`; keep each value as an inline
|
|
163
|
-
YAML string, quoting values that resemble numbers, dates, booleans, or YAML
|
|
164
|
-
collections
|
|
165
|
-
- `concurrency.isolation`: use `adaptive`; a clean serial task works directly on
|
|
166
|
-
the current branch, while dirty or parallel write work uses isolated worktrees
|
|
167
|
-
- `concurrency.base_ref` and `target_branch`: leave blank to derive the current
|
|
168
|
-
upstream, or set them explicitly for a fixed integration branch
|
|
169
|
-
- `concurrency.branch_prefix` and `worktree_root`
|
|
170
|
-
- `concurrency.cleanup_merged` and `delete_remote_branch`: keep both enabled to
|
|
171
|
-
remove integrated temporary worktrees and branches
|
|
172
|
-
- `concurrency.disposable_ignored`: add only project-specific ignored cache/build
|
|
173
|
-
paths that may be discarded with a task worktree; ignored data and unknown
|
|
174
|
-
paths block cleanup, including inside initialized submodules
|
|
175
|
-
- one fast `commands.gate_changed`; the default is `git diff --check`
|
|
176
|
-
|
|
177
|
-
Legacy command keys such as `commands.light_gate`, `test`, and `build` remain
|
|
178
|
-
callable explicitly with `ap.py run <name>` but never replace the automatic
|
|
179
|
-
changed gate. `quick_test` remains the only fallback when `gate_changed` is
|
|
180
|
-
absent. Run `doctor` for exact missing-field diagnostics.
|
|
181
|
-
|
|
182
|
-
If the actual changed gate fails only because a dependency already declared in
|
|
183
|
-
the repository lockfile is not installed in the working checkout, restore that
|
|
184
|
-
locked dependency locally (for example with `npm ci`) and rerun the same changed
|
|
185
|
-
gate once. Do not install dependencies or restart a standard/full diagnostic
|
|
186
|
-
that was invoked outside the normal development gate, and never promote this
|
|
187
|
-
recovery into a full-gate run.
|
|
188
|
-
|
|
189
|
-
## Concurrent write tasks
|
|
190
|
-
|
|
191
|
-
For one serial write task, inspect the current checkout first. If it is clean,
|
|
192
|
-
develop directly on the current branch, run the changed gate once, commit, and
|
|
193
|
-
push without creating a temporary branch. If it already contains changes, or if
|
|
194
|
-
multiple writers will run concurrently, preserve the checkout and use one
|
|
195
|
-
registered task branch/worktree per writer. Never share one worktree between
|
|
196
|
-
writers. Clean temporary worktrees and merged task branches after integration.
|
|
94
|
+
<!-- auto-coding-skill:managed-workflow:start version=4.1.0 -->
|
|
95
|
+
|
|
96
|
+
This file contains project facts and the small amount of configuration the
|
|
97
|
+
generic workflow cannot infer. Normal delivery is:
|
|
98
|
+
|
|
99
|
+
`analysis → decomposition → necessary design → development → one final fast
|
|
100
|
+
changed-scope gate → commit/push`.
|
|
101
|
+
|
|
102
|
+
Target-branch push ends normal coding. Jenkins, deployment, and owner acceptance
|
|
103
|
+
happen later. When the user explicitly asks to diagnose a failure caused by the
|
|
104
|
+
pushed change, diagnosis and repair may continue in the same conversation and
|
|
105
|
+
task scope without creating another taskbook/lifecycle entry.
|
|
106
|
+
|
|
107
|
+
The Skill is a selectable set of guardrails, not a requirement to execute every
|
|
108
|
+
command on every task. Read-only work, obvious clean-checkout changes, and pure
|
|
109
|
+
ledger/archive reconciliation normally skip classify, task-start, durable design,
|
|
110
|
+
reviewer, and subagents. Use each mechanism only when its expected quality or
|
|
111
|
+
throughput benefit is greater than its coordination cost.
|
|
112
|
+
|
|
113
|
+
## Delivery levels
|
|
114
|
+
|
|
115
|
+
| Level | Default behavior | Added guardrails |
|
|
116
|
+
| --- | --- | --- |
|
|
117
|
+
| Micro | main agent, current branch, fast route | none |
|
|
118
|
+
| Standard | main agent or justified read-only help | no mandatory reviewer or design document |
|
|
119
|
+
| High risk | focused design and independent review | only the affected validation routes |
|
|
120
|
+
| Parallel | one isolated writer per unit | owned paths, dependency SHAs, leases, fingerprint review, ordered integration |
|
|
121
|
+
|
|
122
|
+
Risk changes analysis, design, and review depth. It never promotes normal local
|
|
123
|
+
development to a full repository build, Docker run, Jenkins poll, deployment, or
|
|
124
|
+
target-environment acceptance.
|
|
125
|
+
|
|
126
|
+
## Adaptive isolation
|
|
127
|
+
|
|
128
|
+
Run task planning before development:
|
|
197
129
|
|
|
198
130
|
```bash
|
|
199
|
-
python3 docs/tools/autopipeline/ap.py
|
|
200
|
-
--
|
|
201
|
-
[--depends-on <TASK_ID>=<SHA> ...] [--writer <WRITER>]
|
|
202
|
-
# Enter the worktree path printed by task-start.
|
|
203
|
-
python3 docs/tools/autopipeline/ap.py task-status <TASK_ID>
|
|
204
|
-
python3 docs/tools/autopipeline/ap.py task-submodule-sync <TASK_ID>
|
|
205
|
-
python3 docs/tools/autopipeline/ap.py task-review <TASK_ID> \
|
|
206
|
-
--verdict approved --diff-fingerprint <SHA256> [--reviewer <REVIEWER>]
|
|
207
|
-
python3 docs/tools/autopipeline/ap.py task-handoff <TASK_ID> \
|
|
208
|
-
--from <WRITER> --to <WRITER> [--generation <N>]
|
|
209
|
-
python3 docs/tools/autopipeline/ap.py commit-push <TASK_ID> \
|
|
210
|
-
--msg "<TASK_ID>: <summary>" [--writer <WRITER>]
|
|
211
|
-
python3 docs/tools/autopipeline/ap.py task-integrate <TASK_ID>
|
|
212
|
-
python3 docs/tools/autopipeline/ap.py task-resume <TASK_ID>
|
|
131
|
+
python3 docs/tools/autopipeline/ap.py classify --scope auto \
|
|
132
|
+
--planned-path <PATH> --intent "<task intent>" [--writers <N>]
|
|
213
133
|
```
|
|
214
134
|
|
|
215
|
-
|
|
216
|
-
|
|
217
|
-
|
|
218
|
-
|
|
219
|
-
|
|
220
|
-
|
|
221
|
-
|
|
222
|
-
|
|
223
|
-
|
|
224
|
-
|
|
225
|
-
|
|
226
|
-
|
|
227
|
-
|
|
228
|
-
current fingerprint before it runs the single fast gate. `task-integrate` repeats
|
|
229
|
-
the dependency and review checks. If integration stops on a conflict, resolve it
|
|
230
|
-
inside the task worktree, run `task-resume`, obtain a fresh review, and then retry
|
|
231
|
-
integration. A target rebase likewise requires a fresh review.
|
|
232
|
-
|
|
233
|
-
The task commit runs project commit hooks once. The internal backup task-branch
|
|
234
|
-
push skips the pre-push hook; the final target-branch push runs it once.
|
|
235
|
-
`task-integrate` creates no second evidence commit.
|
|
236
|
-
|
|
237
|
-
Successful integration removes the clean worktree and merged local branch, and
|
|
238
|
-
deletes the merged remote task branch by default. Use `task-finish <TASK_ID>` to
|
|
239
|
-
retry cleanup for one integrated task and `task-prune` for registered merged
|
|
240
|
-
tasks left behind. Cleanup must refuse dirty worktrees and unmerged branches.
|
|
241
|
-
Before forced task-worktree removal, recursively require initialized submodules
|
|
242
|
-
to be clean and contain no unknown ignored data, local-only history, or
|
|
243
|
-
unmirrored local branches. A submodule with another linked worktree or an
|
|
244
|
-
unrefreshable remote blocks cleanup. Before forced worktree removal, persist its
|
|
245
|
-
refs and reflog commits in the managed Git-common-dir submodule recovery store.
|
|
246
|
-
Do not run submodule deinit from a linked task worktree because its shared config
|
|
247
|
-
can alter the primary checkout.
|
|
248
|
-
`task-start` enables worktree-scoped Git config and seeds task-local submodule
|
|
249
|
-
URLs. After changing `.gitmodules`, run `task-submodule-sync` before submodule
|
|
250
|
-
initialization or sync. Resolve relative URLs with Git's current-worktree
|
|
251
|
-
default-remote semantics. If shared/common submodule config changed after task
|
|
252
|
-
start, report and stop without restoring or overwriting it. Residual module Git
|
|
253
|
-
directories from a manual deinit or removal block forced cleanup until they are
|
|
254
|
-
reinitialized or recovered.
|
|
255
|
-
Integration must not update the primary checkout; pull it explicitly only when
|
|
256
|
-
its user-owned state is ready.
|
|
257
|
-
|
|
258
|
-
Before running `autocoding sync`, finish, integrate, and clean every registered
|
|
259
|
-
v3.0 task with the currently installed 3.0.0 runtime. Sync atomically rejects the
|
|
260
|
-
whole project batch while any schema-v1 task remains, including
|
|
261
|
-
`--components skill`; it never guesses or auto-claims owned paths during upgrade.
|
|
262
|
-
|
|
263
|
-
## Subagent orchestration
|
|
264
|
-
|
|
265
|
-
The main agent owns the task graph and Git lifecycle. Before dispatch, decompose
|
|
266
|
-
the request into bounded units and record for each unit its task ID, role, scope,
|
|
267
|
-
dependencies, acceptance criteria, and expected result. Run only independent
|
|
268
|
-
work concurrently.
|
|
269
|
-
|
|
270
|
-
1. Run justified `explorer`, `docs_researcher`, and `browser_debugger` roles in
|
|
271
|
-
parallel for read-only discovery. Browser work collects reproduction evidence;
|
|
272
|
-
it is not post-push acceptance.
|
|
273
|
-
2. The main agent merges discovery evidence and decides the design, dependency
|
|
274
|
-
graph, and non-overlapping path ownership.
|
|
275
|
-
3. Assign each independent write unit to exactly one `fixer`. A single serial
|
|
276
|
-
fixer may use a clean current branch; dirty checkouts and parallel fixers each
|
|
277
|
-
require a registered task branch/worktree. Never run two writers in one worktree.
|
|
278
|
-
Do not let the main agent edit a fixer-owned worktree concurrently.
|
|
279
|
-
4. Parallelize fixer units only when they are dependency-free and their owned
|
|
280
|
-
paths do not overlap. Complete implementation → review → gate/integration for
|
|
281
|
-
the current dependency wave, then start the next wave only after its
|
|
282
|
-
prerequisites are integrated into the target branch.
|
|
283
|
-
5. A read-only `reviewer` checks a stable diff after implementation and binds its
|
|
284
|
-
verdict to the diff fingerprint. Blocking findings return to the owning fixer;
|
|
285
|
-
any edit invalidates approval and requires re-review. Record the final verdict
|
|
286
|
-
with `task-review` before handing the writer lease back to the main agent.
|
|
287
|
-
6. Subagents never commit, push, integrate, clean branches, or run the project
|
|
288
|
-
gate. Their versioned result contains node/task/role, base SHA, status,
|
|
289
|
-
dependencies, owned and changed paths, diff fingerprint, evidence, findings,
|
|
290
|
-
verdict, risks, and next owner. Read-only roles return no changed paths.
|
|
291
|
-
7. After all required results return, use `task-handoff` to transfer the lease to
|
|
292
|
-
the main agent. The main agent alone runs `commit-push` for each write task,
|
|
293
|
-
which validates the current review and runs the single fast gate, then
|
|
294
|
-
integrates in dependency order, pushes, and cleans all temporary branches and
|
|
295
|
-
worktrees.
|
|
296
|
-
|
|
297
|
-
`classify` emits a machine-readable `agent_plan` with this stage and ownership
|
|
298
|
-
contract. Micro tasks remain main-agent-only unless useful independent work
|
|
299
|
-
clearly exceeds delegation overhead. If the client cannot run subagents, execute
|
|
300
|
-
the same stages sequentially and check for a clean current branch before creating
|
|
301
|
-
any temporary worktree.
|
|
302
|
-
|
|
303
|
-
## Default workflow
|
|
304
|
-
|
|
305
|
-
Development:
|
|
306
|
-
|
|
307
|
-
1. Read this file and the active task entry.
|
|
308
|
-
2. Analyze and decompose the request; run or reason through `classify --scope auto`.
|
|
309
|
-
3. Fan out independent discovery roles, then fan their results back into one main-agent design.
|
|
310
|
-
4. Record the smallest useful design note; create DD/ADR only when indicated.
|
|
311
|
-
5. Use the clean current branch for one serial writer; only dirty or parallel work starts registered worktrees with explicit owned paths, dependency SHAs, and writer leases.
|
|
312
|
-
6. Review stable diffs, record their fingerprints with `task-review`, and return findings to their owning fixers until approved.
|
|
313
|
-
7. Hand the writer lease to the main agent. The main agent runs `commit-push` for each write task; it enforces ownership,
|
|
314
|
-
dependency, lease, and current-review gates, executes the one changed-scope fast gate, records
|
|
315
|
-
`DEV-CLOSED`, commits, and pushes the task branch.
|
|
316
|
-
8. The main agent runs `task-integrate` in dependency order to push the target branch and clean the task worktree and
|
|
317
|
-
merged task branches. This completes the push stage and ends the coding task.
|
|
318
|
-
|
|
319
|
-
Do not wait for, poll, diagnose, or record Jenkins/build/deploy results after the
|
|
320
|
-
push. The project owner performs real acceptance separately.
|
|
321
|
-
|
|
322
|
-
The authoritative order is analysis, decomposition, design, development, fast
|
|
323
|
-
local gate, then push. Do not mark unexecuted external checks as PASS.
|
|
324
|
-
|
|
325
|
-
## Structure policy
|
|
326
|
-
|
|
327
|
-
Generic structure checks are advisory by default. They may report file size,
|
|
328
|
-
function size, or regex-based import-boundary signals, but they block only when
|
|
329
|
-
`structure.enforcement: blocking` is explicitly configured. Repository-native
|
|
330
|
-
architecture and compiler/test evidence take precedence over generic naming
|
|
331
|
-
heuristics. Reuse existing helpers and avoid adding unrelated responsibilities
|
|
332
|
-
to already large files; do not split code merely to satisfy a line count.
|
|
333
|
-
|
|
334
|
-
Use `baseline init --write --update-config` for repository-wide structural work.
|
|
335
|
-
Accepted historical debt belongs in the generated baseline/backlog.
|
|
336
|
-
|
|
337
|
-
## Core and optional documents
|
|
338
|
-
|
|
339
|
-
The default scaffold contains only this file, taskbook, and closure log. Create
|
|
340
|
-
specialized documents when the task needs them:
|
|
135
|
+
- A clean checkout with one writer uses the current branch directly.
|
|
136
|
+
- A checkout that already contains unrelated changes uses an isolated task
|
|
137
|
+
branch/worktree.
|
|
138
|
+
- Two or more concurrent writers always use separate task IDs/worktrees with
|
|
139
|
+
non-overlapping owned paths; each `task-start` creates exactly one writer lease.
|
|
140
|
+
- A task that produces no diff creates no commit or push; direct mode creates no
|
|
141
|
+
temporary branch at all.
|
|
142
|
+
- Never restore, reset, stash, clean, or otherwise modify unknown user or task
|
|
143
|
+
changes.
|
|
144
|
+
|
|
145
|
+
`task-start` implements this decision. Use `--isolated` to force a worktree and
|
|
146
|
+
`--review-required` when a project rule or the task risk requires fingerprinted
|
|
147
|
+
review:
|
|
341
148
|
|
|
342
149
|
```bash
|
|
343
|
-
python3 docs/tools/autopipeline/ap.py
|
|
344
|
-
|
|
345
|
-
python3 docs/tools/autopipeline/ap.py
|
|
346
|
-
python3 docs/tools/autopipeline/ap.py scaffold review --write
|
|
347
|
-
python3 docs/tools/autopipeline/ap.py scaffold testing --write
|
|
348
|
-
python3 docs/tools/autopipeline/ap.py scaffold deployment --write
|
|
349
|
-
python3 docs/tools/autopipeline/ap.py scaffold bugs --write
|
|
350
|
-
python3 docs/tools/autopipeline/ap.py scaffold all --write
|
|
150
|
+
python3 docs/tools/autopipeline/ap.py task-start T0001 \
|
|
151
|
+
--owned-path src --writers 1
|
|
152
|
+
python3 docs/tools/autopipeline/ap.py commit-push T0001 --msg "T0001: summary"
|
|
351
153
|
```
|
|
352
154
|
|
|
353
|
-
|
|
354
|
-
|
|
355
|
-
`
|
|
155
|
+
In direct mode, `commit-push` runs the final gate, commits, and pushes the current
|
|
156
|
+
target branch. In isolated mode it pushes the task branch; the main agent then
|
|
157
|
+
runs `task-integrate`, which pushes the target branch and removes clean merged
|
|
158
|
+
temporary branches/worktrees. `task-prune` removes only safely merged leftovers.
|
|
356
159
|
|
|
357
|
-
##
|
|
160
|
+
## Real changed-scope validation
|
|
358
161
|
|
|
359
|
-
|
|
360
|
-
|
|
361
|
-
|
|
362
|
-
|
|
363
|
-
|
|
364
|
-
|
|
365
|
-
|
|
366
|
-
|
|
367
|
-
|
|
368
|
-
|
|
369
|
-
|
|
370
|
-
|
|
371
|
-
|
|
372
|
-
|
|
373
|
-
|
|
374
|
-
|
|
375
|
-
|
|
162
|
+
`risk.rules` classifies work. `validation.routes` executes checks. Do not mix
|
|
163
|
+
these responsibilities.
|
|
164
|
+
|
|
165
|
+
```yaml
|
|
166
|
+
commands:
|
|
167
|
+
backend_fast: "cd backend && go test ./internal/orders/..."
|
|
168
|
+
frontend_fast: "cd frontend && npm run test:changed"
|
|
169
|
+
|
|
170
|
+
validation:
|
|
171
|
+
on_unmapped: error
|
|
172
|
+
routes:
|
|
173
|
+
- name: backend
|
|
174
|
+
paths: ["backend/**", "contracts/**"]
|
|
175
|
+
commands: [backend_fast]
|
|
176
|
+
- name: frontend
|
|
177
|
+
paths: ["frontend/**"]
|
|
178
|
+
commands: [frontend_fast]
|
|
376
179
|
```
|
|
377
180
|
|
|
378
|
-
|
|
379
|
-
|
|
380
|
-
|
|
181
|
+
Every changed path may match multiple routes. The runtime collects all commands
|
|
182
|
+
in configuration order, removes duplicates, and executes each once. Unmapped
|
|
183
|
+
code fails before staging. Documentation-only changes may use the built-in diff
|
|
184
|
+
check. `git diff --check` is always an additional hygiene check and never counts
|
|
185
|
+
as business-code validation.
|
|
186
|
+
|
|
187
|
+
Inspect coverage without running the commands:
|
|
188
|
+
|
|
189
|
+
```bash
|
|
190
|
+
python3 docs/tools/autopipeline/ap.py validation-map-check --path backend/foo.go
|
|
191
|
+
python3 docs/tools/autopipeline/ap.py validation-map-check --tracked
|
|
192
|
+
```
|
|
381
193
|
|
|
382
|
-
|
|
383
|
-
|
|
194
|
+
Focused tests may be run and rerun during implementation. The "one gate" rule
|
|
195
|
+
means one final routed closure gate after the diff is stable; it does not prohibit
|
|
196
|
+
reasonable test/fix/retest cycles. Do not install dependencies proactively. Only
|
|
197
|
+
after the selected final route fails because a repository-locked dependency is
|
|
198
|
+
absent may it be restored once; then retry only that affected route.
|
|
199
|
+
|
|
200
|
+
## Design, review, and subagents
|
|
201
|
+
|
|
202
|
+
- Create DD/ADR only for lasting cross-module, API, data, security, deployment,
|
|
203
|
+
or key user-flow decisions.
|
|
204
|
+
- Ordinary work defaults to the main agent. Delegate only independent discovery
|
|
205
|
+
or implementation units whose latency or expertise benefit exceeds dispatch
|
|
206
|
+
cost.
|
|
207
|
+
- Read-only explorer/docs/browser roles may run in parallel when their questions
|
|
208
|
+
are independent.
|
|
209
|
+
- Parallel fixers require separate worktrees and non-overlapping owned paths.
|
|
210
|
+
- Require reviewer fingerprint approval for high-risk, cross-module, explicitly
|
|
211
|
+
configured, or parallel integration work; ordinary serial fixes do not require it.
|
|
212
|
+
- The main agent alone owns the final gate, commit, push, ordered integration,
|
|
213
|
+
and temporary-branch cleanup.
|
|
214
|
+
|
|
215
|
+
## Documentation framework and lightweight records
|
|
216
|
+
|
|
217
|
+
This managed block and the installed Skill define the shared workflow. Content
|
|
218
|
+
outside this block may describe project facts only: product/domain boundaries,
|
|
219
|
+
repository ownership, runtime/deployment topology, external-system safety,
|
|
220
|
+
validation commands, and links to current contracts/decisions. It must not
|
|
221
|
+
duplicate delivery levels, agent roles, task lifecycle, gate semantics, or
|
|
222
|
+
completion rules.
|
|
223
|
+
|
|
224
|
+
When project facts are too large for this file, scaffold `docs/project/` and link
|
|
225
|
+
those documents here. Code, tests, schemas, migrations, and runtime configuration
|
|
226
|
+
remain authoritative for behavior that exists now; historical records never
|
|
227
|
+
override them.
|
|
228
|
+
|
|
229
|
+
Ordinary tasks do not create taskbook, closure Markdown, evidence JSONL, or active
|
|
230
|
+
task documents. Isolated-task coordination state lives under the Git common
|
|
231
|
+
directory and gate timing lives under `.local/auto-coding-skill`. Existing project
|
|
232
|
+
ledgers are user data: upgrades preserve them but do not require or update them.
|
|
233
|
+
Use `record-closure`, documentation scaffolds, or a baseline only when the user or
|
|
234
|
+
task genuinely needs a durable artifact.
|
|
235
|
+
|
|
236
|
+
Pure taskbook, closure, archive, or ledger consistency work is a terminal
|
|
237
|
+
maintenance action. Validate the affected documents and commit once; do not
|
|
238
|
+
create a new active task, review cycle, closure record, or evidence chain for the
|
|
239
|
+
act of closing the previous record.
|
|
240
|
+
|
|
241
|
+
Historical debt does not block product work. Block only new or worsened P0/P1
|
|
242
|
+
issues; keep accepted debt in an optional backlog and address it through explicit
|
|
243
|
+
governance tasks.
|
|
244
|
+
|
|
245
|
+
## Access and explicit diagnostics
|
|
246
|
+
|
|
247
|
+
Fill all URL, username, and password fields under `access.*` during project
|
|
248
|
+
initialization. Direct plaintext values are allowed. The generic workflow neither
|
|
249
|
+
forbids them nor rewrites a project's credential policy.
|
|
250
|
+
|
|
251
|
+
Full regression, structure scans, Docker, Jenkins, API checks, target verification,
|
|
252
|
+
and deployment remain explicit diagnostic commands. Do not run or poll them
|
|
253
|
+
during normal closure. An explicitly requested diagnosis of a failure caused by
|
|
254
|
+
the just-pushed change may stay in the same conversation/task; it does not require
|
|
255
|
+
an artificial second lifecycle record.
|
|
384
256
|
|
|
385
257
|
<!-- auto-coding-skill:managed-workflow:end -->
|