@forwardimpact/schema 0.9.2 → 0.10.1
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.
- package/README.md +15 -7
- package/examples/capabilities/delivery.yaml +12 -4
- package/examples/questions/capabilities/business.yaml +17 -14
- package/examples/questions/capabilities/delivery.yaml +7 -6
- package/examples/questions/capabilities/people.yaml +17 -12
- package/examples/questions/capabilities/reliability.yaml +16 -11
- package/examples/questions/capabilities/scale.yaml +8 -6
- package/examples/questions/skills/architecture_design.yaml +2 -1
- package/examples/questions/skills/cloud_platforms.yaml +6 -6
- package/examples/questions/skills/code_quality.yaml +54 -31
- package/examples/questions/skills/data_modeling.yaml +19 -11
- package/examples/questions/skills/devops.yaml +28 -17
- package/examples/questions/skills/full_stack_development.yaml +39 -21
- package/examples/questions/skills/sre_practices.yaml +38 -22
- package/examples/questions/skills/stakeholder_management.yaml +41 -25
- package/examples/questions/skills/team_collaboration.yaml +37 -26
- package/examples/questions/skills/technical_writing.yaml +41 -26
- package/examples/stages.yaml +13 -7
- package/package.json +2 -2
- package/src/modifiers.js +1 -1
package/examples/stages.yaml
CHANGED
|
@@ -18,15 +18,19 @@
|
|
|
18
18
|
label: Create Plan
|
|
19
19
|
prompt: Create plan.md based on spec.md.
|
|
20
20
|
constraints:
|
|
21
|
-
- Do not
|
|
21
|
+
- Do not write implementation code or execute system commands
|
|
22
22
|
- Focus on WHAT users need and WHY, not HOW to implement
|
|
23
23
|
- Write specifications as markdown files under specs/[feature-name]/spec.md
|
|
24
|
-
-
|
|
24
|
+
- Before writing the spec, conduct an interactive Q&A session with the user
|
|
25
|
+
- Ask each critical question one at a time and WAIT for answers
|
|
26
|
+
- You MUST ask questions interactively — do NOT embed unanswered questions
|
|
27
|
+
- Only after the user has answered your critical questions should you write
|
|
28
|
+
the spec document
|
|
25
29
|
- No technology choices, APIs, or code structure in specifications
|
|
26
30
|
readChecklist: []
|
|
27
31
|
confirmChecklist:
|
|
28
32
|
- spec.md exists with user stories and acceptance criteria
|
|
29
|
-
- No unresolved
|
|
33
|
+
- No unresolved or open questions in spec.md
|
|
30
34
|
|
|
31
35
|
- id: plan
|
|
32
36
|
name: Plan
|
|
@@ -46,7 +50,7 @@
|
|
|
46
50
|
label: Set Up Environment
|
|
47
51
|
prompt: Prepare the development environment based on plan.md requirements.
|
|
48
52
|
constraints:
|
|
49
|
-
- Do not
|
|
53
|
+
- Do not write implementation code or execute system commands
|
|
50
54
|
- Every technology choice must trace back to a specific requirement
|
|
51
55
|
- Write plans as markdown files under specs/[feature-name]/plan.md
|
|
52
56
|
- Define contracts and data models before implementation details
|
|
@@ -54,10 +58,10 @@
|
|
|
54
58
|
readChecklist: []
|
|
55
59
|
confirmChecklist:
|
|
56
60
|
- spec.md exists with user stories and acceptance criteria
|
|
57
|
-
- No unresolved
|
|
61
|
+
- No unresolved or open questions in spec.md
|
|
58
62
|
- plan.md exists with technology choices and architecture
|
|
59
63
|
- Contracts and data models defined where applicable
|
|
60
|
-
- No unresolved
|
|
64
|
+
- No unresolved or open questions in plan.md
|
|
61
65
|
|
|
62
66
|
- id: onboard
|
|
63
67
|
name: Onboard
|
|
@@ -88,7 +92,9 @@
|
|
|
88
92
|
readChecklist: []
|
|
89
93
|
confirmChecklist:
|
|
90
94
|
- plan.md exists with technology choices and architecture
|
|
91
|
-
- No unresolved
|
|
95
|
+
- No unresolved or open questions in plan.md
|
|
96
|
+
- Install scripts (scripts/install.sh) executed for all skills that provide
|
|
97
|
+
them
|
|
92
98
|
- All dependencies installed and versions verified
|
|
93
99
|
- Environment variables and secrets configured (.env files, tokens)
|
|
94
100
|
- Linter and formatter configured and passing on existing code
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@forwardimpact/schema",
|
|
3
|
-
"version": "0.
|
|
4
|
-
"description": "
|
|
3
|
+
"version": "0.10.1",
|
|
4
|
+
"description": "Public data model for career frameworks, consumed by AI agents and engineers",
|
|
5
5
|
"license": "Apache-2.0",
|
|
6
6
|
"repository": {
|
|
7
7
|
"type": "git",
|
package/src/modifiers.js
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
* Skill Modifier Helpers for Validation
|
|
3
3
|
*
|
|
4
4
|
* Contains only the isCapability function needed for schema validation.
|
|
5
|
-
* Full modifier logic is in @forwardimpact/
|
|
5
|
+
* Full modifier logic is in @forwardimpact/libpathway.
|
|
6
6
|
*/
|
|
7
7
|
|
|
8
8
|
import { Capability } from "./levels.js";
|