agent-context-store 0.2.9 → 0.2.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (5) hide show
  1. package/agent-config/skills/acs-ba/SKILL.md +24 -4
  2. package/agent-config/skills/acs-dev/SKILL.md +26 -6
  3. package/agent-config/skills/acs-qa/SKILL.md +44 -8
  4. package/agent-config/skills/acs-sa/SKILL.md +27 -7
  5. package/package.json +2 -2
package/agent-config/skills/acs-ba/SKILL.md CHANGED
@@ -32,7 +32,27 @@ acs validate --role ba --task TASK-123
32
32
 
33
33
  Do not proceed until validation passes.
34
34
 
35
- ## 4. Hand Off to SA
35
+ ## 4. Request Approval
36
+
37
+ Ask the user or responsible stakeholder to review and approve the BA artifacts before handoff.
38
+
39
+ Do not create the SA handoff until all required BA artifacts are approved:
40
+
41
+ - SRS
42
+ - User story
43
+ - Acceptance criteria
44
+
45
+ If approval is granted, update each BA artifact frontmatter so `status: approved` and `approval_status: approved`.
46
+
47
+ Then re-run validation:
48
+
49
+ ```bash
50
+ acs validate --role ba --task TASK-123
51
+ ```
52
+
53
+ If approval is not granted, capture the requested changes in the artifacts and repeat validation before asking again.
54
+
55
+ ## 5. Hand Off to SA
36
56
 
37
57
  ```bash
38
58
  acs handoff create --from ba --to sa --task TASK-123
@@ -40,14 +60,14 @@ acs package --task TASK-123 --role sa
40
60
  acs index
41
61
  ```
42
62
 
43
- ## 5. Output Handoff Prompt
63
+ ## 6. Output Handoff Prompt
44
64
 
45
- End your response with this prompt for the SA agent:
65
+ Only after approval and handoff creation succeed, end your response with this prompt for the SA agent:
46
66
 
47
67
  ```
48
68
  [HANDOFF: BA → SA | TASK-123]
49
69
 
50
- The BA role has completed requirements for TASK-123.
70
+ The BA role has completed and received approval for requirements for TASK-123.
51
71
 
52
72
  Artifacts ready for you:
53
73
  - <path to SRS artifact>
package/agent-config/skills/acs-dev/SKILL.md CHANGED
@@ -19,13 +19,14 @@ acs handoff check --from sa --to dev --task TASK-123
19
19
  acs package --task TASK-123 --role dev
20
20
  ```
21
21
 
22
- ## 2. Create Implementation Note
22
+ ## 2. Create DEV Artifacts
23
23
 
24
24
  ```bash
25
25
  acs dev new implementation-note --task TASK-123
26
+ acs dev new unit-test-note --task TASK-123
26
27
  ```
27
28
 
28
- **Fill every section immediately** — document implementation decisions, deviations from the design, and any constraints discovered during development. List consulted files under `source_refs`. Complete the Validation Checklist at the end of the file.
29
+ **Fill every section immediately** — document implementation decisions, deviations from the design, unit test coverage, and any constraints discovered during development. List consulted files under `source_refs`. Complete the Validation Checklist at the end of each file.
29
30
 
30
31
  ## 3. Validate
31
32
 
@@ -35,7 +36,24 @@ acs validate --role dev --task TASK-123
35
36
 
36
37
  Do not proceed until validation passes.
37
38
 
38
- ## 4. Hand Off to QA
39
+ ## 4. Mark Ready for Review
40
+
41
+ Do not create the QA handoff until all required DEV artifacts are ready for review:
42
+
43
+ - Implementation note
44
+ - Unit test note
45
+
46
+ Update each DEV artifact frontmatter so `status: ready_for_review`. Keep `approval_status: pending` unless a reviewer explicitly changes it.
47
+
48
+ Then re-run validation:
49
+
50
+ ```bash
51
+ acs validate --role dev --task TASK-123
52
+ ```
53
+
54
+ If the work is not ready for review, capture the remaining tasks or blockers in the artifacts and repeat validation before handoff.
55
+
56
+ ## 5. Hand Off to QA
39
57
 
40
58
  ```bash
41
59
  acs handoff create --from dev --to qa --task TASK-123
@@ -43,9 +61,9 @@ acs package --task TASK-123 --role qa
43
61
  acs index
44
62
  ```
45
63
 
46
- ## 5. Output Handoff Prompt
64
+ ## 6. Output Handoff Prompt
47
65
 
48
- End your response with this prompt for the QA agent:
66
+ Only after the artifacts are marked ready for review and handoff creation succeeds, end your response with this prompt for the QA agent:
49
67
 
50
68
  ```
51
69
  [HANDOFF: DEV → QA | TASK-123]
@@ -54,14 +72,16 @@ The DEV role has completed implementation for TASK-123.
54
72
 
55
73
  Artifacts ready for you:
56
74
  - <path to implementation note>
75
+ - <path to unit test note>
57
76
 
58
77
  Context package: <path printed by acs package>
59
78
 
60
79
  Your next steps (QA role):
61
80
  1. Read the context package above.
62
81
  2. Run: acs role explain qa --task TASK-123
63
- 3. Create your test plan: acs qa new test-plan --task TASK-123 --title "<title>"
82
+ 3. Create QA artifacts: acs qa new test-plan --task TASK-123 --title "<title>" and acs qa new qa-signoff --task TASK-123 --title "<title>"
64
83
  4. Fill all sections, then validate: acs validate --role qa --task TASK-123
84
+ 5. After approval, mark QA artifacts approved and hand off to SA: acs handoff create --from qa --to sa --task TASK-123
65
85
 
66
86
  Open questions from DEV (resolve before or during testing):
67
87
  - <list any open questions from the implementation note>
package/agent-config/skills/acs-qa/SKILL.md CHANGED
@@ -19,34 +19,70 @@ acs handoff check --from dev --to qa --task TASK-123
19
19
  acs package --task TASK-123 --role qa
20
20
  ```
21
21
 
22
- ## 2. Create Test Plan
22
+ ## 2. Create QA Artifacts
23
23
 
24
24
  ```bash
25
25
  acs qa new test-plan --task TASK-123 --title "Feature test plan"
26
+ acs qa new qa-signoff --task TASK-123 --title "Feature QA signoff"
26
27
  ```
27
28
 
28
- **Fill every section immediately** — document test scope, test cases, acceptance criteria, and any risks. List consulted files under `source_refs`. Complete the Validation Checklist at the end of the file.
29
+ **Fill every section immediately** — document test scope, test cases, acceptance criteria, signoff decision, and any risks. List consulted files under `source_refs`. Complete the Validation Checklist at the end of each file.
29
30
 
30
31
  ## 3. Validate
31
32
 
32
33
  ```bash
33
34
  acs validate --role qa --task TASK-123
35
+ ```
36
+
37
+ Do not proceed until validation passes.
38
+
39
+ ## 4. Request Approval
40
+
41
+ Ask the user or responsible stakeholder to review and approve the QA artifacts before handoff.
42
+
43
+ Do not create the SA handoff until all required QA artifacts are approved:
44
+
45
+ - Test plan
46
+ - QA signoff
47
+
48
+ If approval is granted, update each QA artifact frontmatter so `status: approved` and `approval_status: approved`.
49
+
50
+ Then re-run validation:
51
+
52
+ ```bash
53
+ acs validate --role qa --task TASK-123
54
+ ```
55
+
56
+ If approval is not granted, capture the requested changes in the artifacts and repeat validation before asking again.
57
+
58
+ ## 5. Hand Off to SA
59
+
60
+ ```bash
61
+ acs handoff create --from qa --to sa --task TASK-123
62
+ acs package --task TASK-123 --role sa
34
63
  acs index
35
64
  ```
36
65
 
37
- ## 4. Output Completion Report
66
+ ## 6. Output Handoff Prompt
38
67
 
39
- QA is the final role in the workflow. End your response with a completion summary:
68
+ Only after approval and handoff creation succeed, end your response with this prompt for the SA agent:
40
69
 
41
70
  ```
42
- [COMPLETE: QA | TASK-123]
71
+ [HANDOFF: QA → SA | TASK-123]
43
72
 
44
- QA has completed the test plan for TASK-123.
73
+ The QA role has completed and received approval for QA validation for TASK-123.
45
74
 
46
- Artifacts produced:
75
+ Artifacts ready for you:
47
76
  - <path to test plan>
77
+ - <path to QA signoff>
78
+
79
+ Context package: <path printed by acs package>
48
80
 
49
- Full artifact index: run `acs index` to view all artifacts and handoffs for this task.
81
+ Your next steps (SA role):
82
+ 1. Read the context package above.
83
+ 2. Run: acs role explain sa --task TASK-123
84
+ 3. Create the release readiness report: acs sa new release-readiness-report --task TASK-123 --title "<title>"
85
+ 4. Fill all sections, then validate: acs validate --role sa --task TASK-123
50
86
 
51
87
  Outstanding issues or risks:
52
88
  - <list any issues found during QA, or "None">
package/agent-config/skills/acs-sa/SKILL.md CHANGED
@@ -21,7 +21,7 @@ acs package --task TASK-123 --role sa
21
21
 
22
22
  ## 2. Create SA Artifacts
23
23
 
24
- Create one or more of the following based on the task scope:
24
+ Create the required SA artifacts before handing off to DEV:
25
25
 
26
26
  ```bash
27
27
  acs sa new sdd --task TASK-123 --title "Feature system design"
@@ -39,7 +39,27 @@ acs validate --role sa --task TASK-123
39
39
 
40
40
  Do not proceed until validation passes.
41
41
 
42
- ## 4. Hand Off to DEV
42
+ ## 4. Request Approval
43
+
44
+ Ask the user or responsible stakeholder to review and approve the SA design artifacts before handoff.
45
+
46
+ Do not create the DEV handoff until all required design artifacts are approved:
47
+
48
+ - SDD
49
+ - ADR
50
+ - API design
51
+
52
+ If approval is granted, update each SA artifact frontmatter so `status: approved` and `approval_status: approved`.
53
+
54
+ Then re-run validation:
55
+
56
+ ```bash
57
+ acs validate --role sa --task TASK-123
58
+ ```
59
+
60
+ If approval is not granted, capture the requested changes in the artifacts and repeat validation before asking again.
61
+
62
+ ## 5. Hand Off to DEV
43
63
 
44
64
  ```bash
45
65
  acs handoff create --from sa --to dev --task TASK-123
@@ -47,14 +67,14 @@ acs package --task TASK-123 --role dev
47
67
  acs index
48
68
  ```
49
69
 
50
- ## 5. Output Handoff Prompt
70
+ ## 6. Output Handoff Prompt
51
71
 
52
- End your response with this prompt for the DEV agent:
72
+ Only after approval and handoff creation succeed, end your response with this prompt for the DEV agent:
53
73
 
54
74
  ```
55
75
  [HANDOFF: SA → DEV | TASK-123]
56
76
 
57
- The SA role has completed the system design for TASK-123.
77
+ The SA role has completed and received approval for the system design for TASK-123.
58
78
 
59
79
  Artifacts ready for you:
60
80
  - <paths to SDD / ADR / API design artifacts>
@@ -64,9 +84,9 @@ Context package: <path printed by acs package>
64
84
  Your next steps (DEV role):
65
85
  1. Read the context package above.
66
86
  2. Run: acs role explain dev --task TASK-123
67
- 3. Create your implementation note: acs dev new implementation-note --task TASK-123
87
+ 3. Create implementation artifacts: acs dev new implementation-note --task TASK-123 and acs dev new unit-test-note --task TASK-123
68
88
  4. Fill all sections, then validate: acs validate --role dev --task TASK-123
69
- 5. When done, hand off to QA: acs handoff create --from dev --to qa --task TASK-123
89
+ 5. Mark DEV artifacts `status: ready_for_review`, re-validate, then hand off to QA: acs handoff create --from dev --to qa --task TASK-123
70
90
 
71
91
  Open questions from SA (resolve before or during implementation):
72
92
  - <list any open questions from the design artifacts>
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "agent-context-store",
3
- "version": "0.2.9",
3
+ "version": "0.2.10",
4
4
  "description": "acs CLI for Agent Context Store Toolkit.",
5
5
  "type": "module",
6
6
  "license": "MIT",
@@ -23,7 +23,7 @@
23
23
  },
24
24
  "dependencies": {
25
25
  "@inquirer/prompts": "^8.4.2",
26
- "agent-context-store-core": "0.2.9"
26
+ "agent-context-store-core": "0.2.10"
27
27
  },
28
28
  "scripts": {
29
29
  "build": "tsc -p tsconfig.json"