UNPKG

paqad-ai

Version:

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

github.com/Eliyce/paqad-ai

Eliyce/paqad-ai

58 lines (42 loc) • 2.34 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
58
--- name: site-map-readiness description: 'Grades whether the project is mappable (app kind, frameworks, an extractor that covers its shape) and routes the unmappable case. Use when a site-map run starts; it always runs first.' metadata: model_tier: fast cacheable: 'false' output_format: json paqad-meta: skill.meta.yaml --- ## What It Does Confirms the project is mappable before the workflow spends any effort: the app kind and frameworks are detectable, and at least one extractor covers the app's shape. Emits a readiness verdict (`ready | partial | blocked`) that gates everything downstream. Runs first, like `design-system-coverage` gates the design-test workflow. ## Use This When As the **first skill in every site-map run**. Never run extraction, modeling, or verification without a `ready` or `partial` verdict from it. ## Inputs - Read `.paqad/project-profile.yaml` for the detected `active_capabilities` and `stack_profile`. - Read the project manifests the profile points at (`package.json`, `composer.json`, lockfiles). - Read `references/readiness-criteria.md` before grading. ## Procedure The verdict is a deterministic function of what the engine can detect: drive it from the engine, do not re-derive detection in prose. 1. Run `paqad-ai sitemap run` and read the `readiness` and `blocked_checks` it reports; the engine owns app-kind and framework detection. 2. Grade the verdict: `ready` when an extractor covers the app shape, `partial` when only the generic convention fallback applies, `blocked` when no extractor covers the shape. 3. Emit the readiness inventory (app kind, frameworks, extractor, verdict, blocked reasons). ## Output Contract - A JSON object `{ app_kind, frameworks: [...], extractor, verdict, blocked_checks: [...] }`. - `verdict` ∈ `ready | partial | blocked`. - A `blocked` verdict must carry at least one `blocked_checks` entry with a reason. ## Escalate / Stop Conditions - Stop when the verdict is `blocked`: surface the engine's `blocked_checks` reason and do not fabricate surfaces to fill the gap. - Warn when the verdict is `partial`: downstream skills run in exploratory mode and tag surfaces `confidence: low`. - Do not upgrade a `partial` verdict to `ready` to unblock the run. ## Resources - `references/readiness-criteria.md` - `agents/openai.yaml`