UNPKG

paqad-ai

Version:

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

github.com/Eliyce/paqad-ai

Eliyce/paqad-ai

47 lines (32 loc) • 2.85 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
--- name: development-recipe description: 'The method for the development stage of a full-lane change: stay in scope, map each criterion to a test, run the inner loop, and pause on a decision. Use when you are the paqad development stage agent.' metadata: model_tier: reasoning cacheable: 'false' output_format: markdown paqad-meta: skill.meta.yaml --- ## What It Does Gives the development stage one method: check scope against the frozen spec, map criteria to tests, and keep the inner test loop small. ## Use This When You are the paqad stage agent for this stage. Your injected copy is the truth for this stage; the source skills it copies stay for their other workflows. ## Inputs - The request, `plan.json` and `specification.json` from `paqad-ai stage begin development`. ## Procedure 1. Restate the request and its acceptance criteria in two lines at the top of your return. 2. Implement only the requested feature behavior and avoid unrelated refactors. 3. You may be resumed with a follow-up task for the same change. Keep working from what you already know; do not re-read files you have read unless they changed. 4. Check scope before each area: compare what you are about to change with the frozen spec only. Outside it, stop and open a decision. 5. For each criterion, pick the smallest test layer that proves it, reuse existing test files first, and name the criterion id in the test name or its describe block, so the `check-ac-map.mjs` check finds it on a line this change adds. `check-ac-map.mjs` proves a test names a criterion, not that it tests it. A language with no hyphen in a name can use `ac_1` or `Ac1`. A criterion with `proof: manual` or `proof: visual` needs no test. 6. Inner loop: run only the tests for the files you changed (for vitest, `vitest related <files>`). 7. On a business choice, run `paqad-ai decision create`, on `earlier_check` scan the titles, read up to 5 with `decision check <id> --read` and run `decision suggest`, on `"reused": true` carry on as your rules say, and unless it was reused return `paused: D-<id>` and wait to be resumed with the answer. 8. End with `paqad-ai stage end development --agent paqad-development`. It runs the `check-ac-map.mjs` check itself and refuses when a criterion has no test, printing which. ## Read This Path - For the full scope method, read `base/skills/scope-check/SKILL.md` under the install directory that `.paqad/framework-path.txt` names. - For the full test mapping method, read `base/skills/test-per-ac-planner/SKILL.md` under the install directory that `.paqad/framework-path.txt` names. ## Output Contract - The source and test edits, and `rules-loaded.json`. - Every automated criterion named by at least one test. ## Escalate / Stop Conditions - A change the spec does not cover: open a decision. A recipe never resolves one.