UNPKG

paqad-ai

Version:

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

github.com/Eliyce/paqad-ai

Eliyce/paqad-ai

52 lines (37 loc) • 2.26 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
--- name: sequence-planner description: 'Breaks work into ordered, coherent stories. Use when requirements are stable enough to split, above all when database, contract, documentation or UI changes must land in order.' metadata: model_tier: reasoning cacheable: 'false' output_format: markdown paqad-meta: skill.meta.yaml --- ## What It Does Builds a deterministic work sequence that orders stories by dependency, rollback safety, and verification readiness so teams do not discover critical prerequisites too late. ## Use This When After requirements are stable enough to split work, especially when database, contract, documentation, or UI changes must land in a deliberate order. ## Inputs - Read the enriched requirements, acceptance criteria, and any existing plan fragments. - Read the canonical docs for the affected modules and interfaces. - Read `references/sequencing-rules.md` before assigning story boundaries. ## Procedure 1. List prerequisites, irreversible steps, and verification gates implied by the requirements. 2. Group tasks into independently reviewable stories: each must leave the system in a coherent state. 3. Apply the precedence rules in `assets/order-rules.txt` (schema → contracts → registries → flag → code → UI; irreversible steps last per workstream). 4. Attach a single verification focus to each story. 5. Format per `assets/output.template.md`; validate with `scripts/lint-output.sh`. ## Output Contract - Match `assets/output.template.md`: `## Implementation Sequence`, per-story `### Story N: name` numbered sequentially from 1 with Goal/Dependencies/Verification/Reversibility/Blast-radius lines, and `## Sequencing Risks`. - Output must pass `scripts/lint-output.sh` (exit 0). ## Escalate / Stop Conditions - Ask when multiple valid orders exist but the tradeoff depends on release strategy or deployment controls. - Warn when a requested sequence would force unsafe migration or contract timing. - Do not combine unrelated workstreams just to reduce story count. ## Resources - `references/sequencing-rules.md` - `scripts/lint-output.sh` - `assets/output.template.md` - `assets/order-rules.txt` - `runtime/capabilities/coding/checklists/database-review-20pt.md` - `agents/openai.yaml`