UNPKG

paqad-ai

Version:

Spec-driven development framework — AI agents that think before they type

github.com/Eliyce/paqad-ai

Eliyce/paqad-ai

57 lines (42 loc) • 2.5 kB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
--- name: error-catalog-maintainer description: 'Maintains per-module error catalogs. Use when a change adds error codes, changes user-facing messages, or changes the recovery path for an existing failure.' metadata: model_tier: medium max_lines: '200' cacheable: 'false' output_format: markdown paqad-meta: skill.meta.yaml --- ## What It Does Maintains per-module error catalogs so new or changed failure paths are documented with recovery guidance, ownership signals, and registry consistency. ## Use This When When a change introduces new error codes, modifies user-facing messages, or changes the recovery path for existing failures. ## Inputs - Read the module `error-catalog.md` and any API error docs first. - Read the changed implementation and any available error-code extraction output. - Read `references/error-entry-fields.md` before editing catalog entries. ## Procedure 1. Run `scripts/find-error-catalogs.sh` to locate canonical per-module error catalogs. 2. Run `scripts/extract-error-codes.sh <changed-files...>` to surface candidate codes the diff introduces or renames. 3. For each new / changed code, write or update its entry using `assets/entry.template.md` (code, trigger, user message, operator meaning, recovery, retry safety, ownership). 4. Check global registry / module prefix collisions explicitly. 5. Format report per `assets/output.template.md` and validate with `scripts/lint-output.sh`. Vague user messages or unknown recovery → `## Catalog Gaps`, never a completed entry. ## Output Contract - Match `assets/output.template.md`: `## Updated Error Entries` and `## Catalog Gaps`. - Every updated entry must name the error code, catalog path, and changed trigger, message, recovery, or ownership field. - Output must pass `scripts/lint-output.sh` (exit 0). - Unknown recovery guidance, owner, or retry safety belongs under `Catalog Gaps`, never as a guessed completed entry. ## Escalate / Stop Conditions - Ask when the correct user-facing recovery guidance depends on product or support policy. - Warn when an error path leaks internal details or has no documented operator response. - Do not approve an entry that only says a generic failure occurred. ## Resources - `references/error-entry-fields.md` - `scripts/find-error-catalogs.sh` - `scripts/extract-error-codes.sh` - `scripts/lint-output.sh` - `assets/output.template.md` - `assets/entry.template.md` - `runtime/templates/runner-scripts/extract-error-codes.sh.hbs` - `agents/openai.yaml`