@forwardimpact/schema 0.9.1 → 0.10.0

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 (18) hide show
  1. package/examples/capabilities/delivery.yaml +12 -4
  2. package/examples/questions/capabilities/business.yaml +33 -33
  3. package/examples/questions/capabilities/delivery.yaml +31 -34
  4. package/examples/questions/capabilities/people.yaml +33 -31
  5. package/examples/questions/capabilities/reliability.yaml +33 -31
  6. package/examples/questions/capabilities/scale.yaml +33 -32
  7. package/examples/questions/skills/architecture_design.yaml +59 -48
  8. package/examples/questions/skills/cloud_platforms.yaml +54 -42
  9. package/examples/questions/skills/code_quality.yaml +104 -31
  10. package/examples/questions/skills/data_modeling.yaml +51 -39
  11. package/examples/questions/skills/devops.yaml +56 -38
  12. package/examples/questions/skills/full_stack_development.yaml +59 -36
  13. package/examples/questions/skills/sre_practices.yaml +58 -39
  14. package/examples/questions/skills/stakeholder_management.yaml +56 -39
  15. package/examples/questions/skills/team_collaboration.yaml +52 -35
  16. package/examples/questions/skills/technical_writing.yaml +54 -35
  17. package/examples/stages.yaml +13 -7
  18. package/package.json +1 -1
package/examples/questions/skills/team_collaboration.yaml CHANGED
@@ -5,16 +5,17 @@ professionalQuestions:
5
5
  - id: tc_pro_aware_1
6
6
  text: How do you work with your team to complete shared tasks?
7
7
  lookingFor:
8
- - Basic teamwork skills
9
- - Communication practices
8
+ - Communicates progress and blockers to teammates without being asked
9
+ - Shows willingness to help others even when it's not their direct
10
+ responsibility
10
11
  expectedDurationMinutes: 5
11
12
  foundational:
12
13
  - id: tc_pro_found_1
13
- text:
14
- Describe how you've helped a teammate when they were stuck on a problem.
14
+ text: How do you help a teammate when they're stuck on a problem?
15
15
  lookingFor:
16
- - Supportive collaboration
17
- - Knowledge sharing
16
+ - Offers support proactively without waiting to be asked
17
+ - Shares knowledge in a way that builds the teammate's capability
18
+ - Balances helping others with their own delivery commitments
18
19
  expectedDurationMinutes: 5
19
20
  working:
20
21
  - id: tc_pro_work_1
@@ -22,15 +23,18 @@ professionalQuestions:
22
23
  followUps:
23
24
  - How do you handle remote collaboration?
24
25
  lookingFor:
25
- - Active collaboration facilitation
26
- - Team enablement
26
+ - Creates practices that make collaboration easy, like shared
27
+ documentation and regular syncs
28
+ - Adapts collaboration approach for remote and distributed team members
29
+ - Identifies and removes collaboration friction points proactively
27
30
  expectedDurationMinutes: 8
28
31
  practitioner:
29
32
  - id: tc_pro_pract_1
30
- text: Describe how you've built high-performing team dynamics.
33
+ text: How do you build high-performing team dynamics?
31
34
  lookingFor:
32
- - Team building expertise
33
- - Handling interpersonal challenges
35
+ - Creates conditions for psychological safety and productive conflict
36
+ - Addresses interpersonal friction before it undermines collaboration
37
+ - Builds shared goals that unite diverse working styles
34
38
  expectedDurationMinutes: 10
35
39
  expert:
36
40
  - id: tc_pro_expert_1
@@ -38,52 +42,65 @@ professionalQuestions:
38
42
  How do you create collaborative culture across multiple teams or an
39
43
  organization?
40
44
  lookingFor:
41
- - Cross-team collaboration leadership
42
- - Organizational culture shaping
45
+ - Creates cross-team collaboration practices adopted beyond their own
46
+ teams
47
+ - Breaks down silos by establishing shared goals and mutual dependencies
48
+ - Influences organisational culture so collaboration is the default, not
49
+ the exception
43
50
  expectedDurationMinutes: 10
44
51
 
45
52
  managementQuestions:
46
53
  awareness:
47
54
  - id: tc_mgmt_aware_1
48
- text: How do you encourage collaboration within your team?
55
+ text: How do you ensure your team communicates effectively?
49
56
  lookingFor:
50
- - Basic collaboration encouragement
51
- - Team communication awareness
57
+ - Creates clear team communication norms for standups, async updates,
58
+ and escalations
59
+ - Notices when communication breaks down and addresses it promptly
52
60
  expectedDurationMinutes: 5
53
61
  foundational:
54
62
  - id: tc_mgmt_found_1
55
- text: How do you handle conflicts or tensions within your team?
56
- followUps:
57
- - How do you prevent conflicts from escalating?
63
+ text: How do you help team members develop collaboration skills?
58
64
  lookingFor:
59
- - Conflict resolution approach
60
- - Team harmony maintenance
65
+ - Creates opportunities for pair and mob programming to build
66
+ collaboration habits
67
+ - Gives specific feedback on collaboration behaviours in 1:1s and retros
68
+ - Models effective collaboration in their own cross-functional
69
+ interactions
61
70
  expectedDurationMinutes: 5
62
71
  working:
63
72
  - id: tc_mgmt_work_1
64
- text: How do you build psychological safety and trust within your team?
73
+ text: How do you facilitate team collaboration and handle conflicts?
65
74
  followUps:
66
- - How do you measure team health?
75
+ - How do you build psychological safety?
67
76
  lookingFor:
68
- - Psychological safety practices
69
- - Team health monitoring
77
+ - Addresses conflicts early through facilitated discussion rather than
78
+ avoidance
79
+ - Creates psychological safety by responding constructively to mistakes
80
+ and disagreements
81
+ - Builds team practices that encourage healthy debate and productive
82
+ conflict
70
83
  expectedDurationMinutes: 8
71
84
  practitioner:
72
85
  - id: tc_mgmt_pract_1
73
86
  text:
74
- How do you develop collaboration skills and team culture in your team?
75
- followUps:
76
- - How do you onboard new members into the team culture?
87
+ How do you build high-performing team dynamics and sustain them over
88
+ time?
77
89
  lookingFor:
78
- - Team culture development
79
- - Collaboration skill building
90
+ - Creates conditions where teams maintain high performance through
91
+ personnel changes
92
+ - Addresses team health issues before they impact delivery
93
+ - Builds self-managing teams that sustain their own collaboration
94
+ practices
80
95
  expectedDurationMinutes: 10
81
96
  expert:
82
97
  - id: tc_mgmt_expert_1
83
- text:
84
- How do you foster collaborative culture across multiple teams you
85
- influence?
98
+ text: How do you shape organizational collaboration culture across teams?
86
99
  lookingFor:
87
- - Cross-team collaboration leadership
88
- - Organizational culture shaping
100
+ - Defines cross-team collaboration practices adopted across the business
101
+ unit
102
+ - Creates organisational norms that break down team silos and encourage
103
+ knowledge sharing
104
+ - Influences how the organisation values and rewards collaborative
105
+ behaviour
89
106
  expectedDurationMinutes: 10
package/examples/questions/skills/technical_writing.yaml CHANGED
@@ -5,15 +5,16 @@ professionalQuestions:
5
5
  - id: tw_pro_aware_1
6
6
  text: How do you approach documenting your code and work?
7
7
  lookingFor:
8
- - Basic documentation habits
9
- - Understanding of documentation importance
8
+ - Documents work consistently, not just when asked
9
+ - Understands that documentation helps future maintainers
10
10
  expectedDurationMinutes: 5
11
11
  foundational:
12
12
  - id: tw_pro_found_1
13
13
  text: What makes a good README file? Walk me through what you'd include.
14
14
  lookingFor:
15
- - README best practices
16
- - Reader-centric documentation
15
+ - Structures READMEs for the reader's needs, not the author's
16
+ - Includes essentials like purpose, setup, usage, and contribution guide
17
+ - Keeps documentation concise and up-to-date
17
18
  expectedDurationMinutes: 5
18
19
  working:
19
20
  - id: tw_pro_work_1
@@ -21,71 +22,89 @@ professionalQuestions:
21
22
  How do you write technical specifications that enable others to
22
23
  implement features?
23
24
  followUps:
24
- - How detailed do you go?
25
+ - How do you write specs that AI tools can also use effectively?
25
26
  lookingFor:
26
- - Spec writing skills
27
- - Communication of technical requirements
27
+ - Writes specs that reduce ambiguity and enable independent
28
+ implementation
29
+ - Calibrates detail level based on audience and feature complexity
30
+ - Structures specs so they can be verified against implementation
28
31
  expectedDurationMinutes: 8
29
32
  practitioner:
30
33
  - id: tw_pro_pract_1
31
34
  text:
32
35
  How do you establish documentation standards and practices in your team?
33
36
  lookingFor:
34
- - Documentation leadership
35
- - Spec-driven development advocacy
37
+ - Creates documentation standards that the team actually follows because
38
+ they're practical
39
+ - Champions spec-driven development where documentation precedes
40
+ implementation
41
+ - Reviews documentation quality with the same rigour as code reviews
36
42
  expectedDurationMinutes: 8
37
43
  expert:
38
44
  - id: tw_pro_expert_1
39
45
  text: How do you create organizational documentation culture and systems?
40
46
  lookingFor:
41
- - Enterprise documentation strategy
42
- - Knowledge management systems
47
+ - Creates documentation systems and practices adopted across the
48
+ business unit
49
+ - Defines knowledge management approaches that reduce information silos
50
+ at scale
51
+ - Influences organisational culture so documentation is valued as a
52
+ first-class engineering output
43
53
  expectedDurationMinutes: 10
44
54
 
45
55
  managementQuestions:
46
56
  awareness:
47
57
  - id: tw_mgmt_aware_1
48
- text: How do you ensure your team documents their work appropriately?
58
+ text: How do you ensure your team maintains adequate documentation?
49
59
  lookingFor:
50
- - Basic documentation expectations
51
- - Team documentation awareness
60
+ - Sets clear expectations about what must be documented and when
61
+ - Checks for documentation as part of feature completion criteria
52
62
  expectedDurationMinutes: 5
53
63
  foundational:
54
64
  - id: tw_mgmt_found_1
55
- text:
56
- How do you set documentation expectations and standards for your team?
57
- followUps:
58
- - How do you handle resistance to documentation?
65
+ text: How do you help team members improve their technical writing skills?
59
66
  lookingFor:
60
- - Documentation standard setting
61
- - Team buy-in practices
67
+ - Reviews documentation and provides specific, actionable feedback on
68
+ clarity and structure
69
+ - Creates pair-writing or review opportunities to build writing skills
70
+ through practice
71
+ - Models clear writing in their own specs, emails, and documentation
62
72
  expectedDurationMinutes: 5
63
73
  working:
64
74
  - id: tw_mgmt_work_1
65
- text:
66
- How do you balance documentation effort with delivery speed in your
67
- team?
75
+ text: How do you establish documentation standards and ensure consistency?
68
76
  followUps:
69
- - What is the minimum documentation you require?
77
+ - How do you balance documentation effort with delivery?
70
78
  lookingFor:
71
- - Documentation vs velocity trade-offs
72
- - Pragmatic documentation approach
79
+ - Creates practical documentation standards that reduce inconsistency
80
+ without overhead
81
+ - Balances documentation effort against delivery by focusing on
82
+ high-value documentation
83
+ - Ensures documentation stays current through process integration, not
84
+ manual enforcement
73
85
  expectedDurationMinutes: 8
74
86
  practitioner:
75
87
  - id: tw_mgmt_pract_1
76
- text: How do you build a documentation culture within your team?
77
- followUps:
78
- - How do you keep documentation current?
88
+ text:
89
+ How do you drive documentation culture and spec-driven development in
90
+ your team?
79
91
  lookingFor:
80
- - Documentation culture development
81
- - Knowledge management practices
92
+ - Creates team expectation that specs are written before code, not after
93
+ - Makes documentation quality a visible part of team health metrics and
94
+ retrospectives
95
+ - Builds a culture where engineers view documentation as an investment,
96
+ not a chore
82
97
  expectedDurationMinutes: 8
83
98
  expert:
84
99
  - id: tw_mgmt_expert_1
85
100
  text:
86
- How do you drive documentation practices and knowledge sharing across
87
- multiple teams?
101
+ How do you shape organizational documentation practices and knowledge
102
+ management?
88
103
  lookingFor:
89
- - Cross-team documentation leadership
90
- - Organizational knowledge strategy
104
+ - Defines documentation practices and knowledge management systems
105
+ adopted across the business unit
106
+ - Creates organisational standards that reduce information fragmentation
107
+ at enterprise scale
108
+ - Influences how the organisation values and invests in documentation
109
+ infrastructure
91
110
  expectedDurationMinutes: 10
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 make code edits or execute commands
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
- - Mark ambiguities with [NEEDS CLARIFICATION]; ask the user; do not guess
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 [NEEDS CLARIFICATION] markers in spec.md
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 make code edits or execute commands
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 [NEEDS CLARIFICATION] markers in spec.md
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 [NEEDS CLARIFICATION] markers in plan.md
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 [NEEDS CLARIFICATION] markers in plan.md
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,6 +1,6 @@
1
1
  {
2
2
  "name": "@forwardimpact/schema",
3
- "version": "0.9.1",
3
+ "version": "0.10.0",
4
4
  "description": "Schema definitions and data loading for skills, behaviours, and role frameworks",
5
5
  "license": "Apache-2.0",
6
6
  "repository": {