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) • 3.43 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: rollback-safety-planner description: 'Drafts an executable rollback procedure for each story with hard reversibility or wide blast radius before it leaves planning. Use when the story designer has emitted its plan in the graduated or full lanes, and always for migrations.' metadata: model_tier: reasoning cacheable: 'false' output_format: markdown paqad-meta: skill.meta.yaml --- ## What It Does Reads the story plan and selects every story tagged `reversibility: hard` or `blast-radius: wide`. For each, drafts a concrete rollback procedure: trigger condition, time-to-rollback target, step list executable by the on-call without consulting the original implementer, forward-only recovery notes when applicable, and a drill plan. The point is to prevent surprised rollback failures during incidents: an explicit procedure is required before any high-cost story can be marked ready. ## Use This When Immediately after the story-designer emits its plan in the graduated and full lanes. Skip stories where reversibility is `easy` and blast-radius is `isolated`. Always run for migration workflows. ## Inputs - Read the story plan at `story_plan_path` first; identify each story's risk annotation. - Read the spec at `spec_path` when available so the rollback's scope can be validated against documented behavior. - Read canonical module docs in `module_doc_paths` for feature flag names, deployment conventions, and existing rollback patterns. - Read `references/rollback-procedure-template.md` before drafting any procedure so every required field is populated. ## Procedure 1. Run `scripts/select-stories.sh <story_plan_path> [workflow]` to get story ids needing a plan (filters on `reversibility: hard`, `blast-radius: wide`, or workflow=`migration`). 2. For each selected story, draft a procedure with every field in `assets/required-fields.txt` (Trigger, Time-to-rollback, Steps, Verification, Forward-only, Drill). 3. Feature-flag rollouts: list the flag name as step 1; confirm the flag exists in the project's flag registry, never invent one. 4. Data migrations: describe forward-only recovery explicitly and call out permanently-lost data. 5. Every step must be idempotent and verifiable: declare the post-step check inline. 6. Format per `assets/output.template.md`; validate with `scripts/lint-output.sh`. ## Output Contract - Match `assets/output.template.md`: `## Rollback Plans`, per-story `### S-N: name` with the 6 required fields, and a `Coverage:` footer. - When no stories require a rollback plan, output the literal `Rollback Plans: none required (all stories have easy reversibility and isolated blast radius).` - Output must pass `scripts/lint-output.sh` (exit 0). ## Escalate / Stop Conditions - Ask when a story implies operational machinery (kill switch, blue/green deployment, traffic shift) that the project profile does not declare available. - Warn when a step would require the original implementer's tacit knowledge: rewrite until the on-call can run it cold. - Warn when "restore from backup" is proposed without a stated Recovery Point Objective and a verified backup retention window. - Do not mark a procedure complete if any field in the template is left unfilled. ## Resources - `references/rollback-procedure-template.md` - `scripts/select-stories.sh` - `scripts/lint-output.sh` - `assets/output.template.md` - `assets/required-fields.txt` - `agents/openai.yaml`