@forwardimpact/schema 0.4.0 → 0.6.0

package/bin/fit-schema.js

@@ -116,7 +116,7 @@ function formatValidationResults(result) {
 async function runValidate(dataDir) {
   console.log(`🔍 Validating data in: ${dataDir}\n`);
 
-  const { runSchemaValidation, loadAllData } = await import("../lib/index.js");
+  const { runSchemaValidation, loadAllData } = await import("../src/index.js");
 
   // Load data first
   const data = await loadAllData(dataDir, { validate: false });
@@ -144,7 +144,7 @@ async function runValidate(dataDir) {
 async function runGenerateIndex(dataDir) {
   console.log(`📁 Generating index files in: ${dataDir}\n`);
 
-  const { generateAllIndexes } = await import("../lib/index.js");
+  const { generateAllIndexes } = await import("../src/index.js");
 
   const results = await generateAllIndexes(dataDir);
 

package/examples/capabilities/business.yaml

@@ -2,7 +2,7 @@
 
 name: Business
 emojiIcon: 💼
-displayOrder: 8
+ordinalRank: 8
 description: |
   Understanding and driving business value.
   Includes domain knowledge, stakeholder management, strategic thinking,

package/examples/capabilities/delivery.yaml

@@ -2,7 +2,7 @@
 
 name: Delivery
 emojiIcon: 🚀
-displayOrder: 1
+ordinalRank: 1
 description: |
   Building and shipping solutions that solve real problems.
   Encompasses full-stack development, data integration, problem discovery,
@@ -273,16 +273,18 @@ skills:
         url: https://developer.hashicorp.com/terraform/docs
         simpleIcon: terraform
         description: Infrastructure as code tool
-        useWhen: Provisioning and managing cloud infrastructure
+        useWhen: Provisioning and managing cloud infrastructure as code
       - name: CloudFormation
         url: https://docs.aws.amazon.com/cloudformation/
         description: AWS infrastructure as code service
-        useWhen: Managing AWS infrastructure as code
-      - name: Docker
-        url: https://docs.docker.com/
+        useWhen: Managing cloud infrastructure using declarative templates
+      - name: Colima
+        url: https://github.com/abiosoft/colima
         simpleIcon: docker
-        description: Container platform
-        useWhen: Containerizing applications or managing container environments
+        description: Container runtime for macOS with Docker-compatible CLI
+        useWhen:
+          Running containers locally, building images, or containerizing
+          applications
     implementationReference: |
       ## Technology Stack
 

package/examples/capabilities/people.yaml

@@ -2,7 +2,7 @@
 
 name: People
 emojiIcon: 👥
-displayOrder: 6
+ordinalRank: 6
 description: |
   Growing individuals and building effective teams.
   Includes mentoring, coaching, hiring, performance management,

package/examples/capabilities/reliability.yaml

@@ -2,7 +2,7 @@
 
 name: Reliability
 emojiIcon: 🛡️
-displayOrder: 5
+ordinalRank: 5
 description: |
   Ensuring systems are dependable, secure, and observable.
   Includes DevOps practices, security, monitoring, incident response,
@@ -160,12 +160,14 @@ skills:
         url: https://developer.hashicorp.com/terraform/docs
         simpleIcon: terraform
         description: Infrastructure as code tool
-        useWhen: Provisioning and managing cloud infrastructure
-      - name: Docker
-        url: https://docs.docker.com/
+        useWhen: Provisioning and managing cloud infrastructure as code
+      - name: Colima
+        url: https://github.com/abiosoft/colima
         simpleIcon: docker
-        description: Container platform
-        useWhen: Containerizing applications or managing container environments
+        description: Container runtime for macOS with Docker-compatible CLI
+        useWhen:
+          Running containers locally, building images, or containerizing
+          applications
     implementationReference: |
       ## CI/CD Pipeline Stages
 
@@ -189,13 +191,32 @@ skills:
 
       ## Infrastructure as Code
 
-      ### Terraform
+      ### Terraform Workflow
+      ```bash
+      terraform init      # Initialize providers and backend
+      terraform plan      # Preview changes before applying
+      terraform apply     # Apply changes to infrastructure
+      terraform destroy   # Tear down infrastructure
+      ```
+
+      ### Terraform in CI/CD Pipelines
+      1. **Plan on PR**: Run `terraform plan` on pull requests
+      2. **Review output**: Require approval for destructive changes
+      3. **Apply on merge**: Run `terraform apply` after merge to main
+      4. **State locking**: Use remote backend with locking (S3 + DynamoDB)
+
+      ### Terraform Structure
       ```hcl
-      # Define resources declaratively
-      resource "aws_instance" "example" {
-        ami           = "ami-0c55b159cbfafe1f0"
-        instance_type = "t2.micro"
+      # main.tf - Define resources declaratively
+      resource "aws_instance" "app" {
+        ami           = var.ami_id
+        instance_type = var.instance_type
+        tags = { Environment = var.environment }
       }
+
+      # variables.tf - Parameterize for environments
+      variable "environment" { type = string }
+      variable "instance_type" { default = "t3.micro" }
       ```
 
       ### Docker

package/examples/capabilities/scale.yaml

@@ -2,7 +2,7 @@
 
 name: Scale
 emojiIcon: 📐
-displayOrder: 4
+ordinalRank: 4
 description: |
   Building systems that grow gracefully.
   Encompasses architecture, code quality, testing, performance,

package/examples/questions/behaviours/outcome_ownership.yaml

@@ -1,51 +1,228 @@
 # yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/behaviour-questions.schema.json
 
-emerging:
-  - id: own_emerg_1
-    text: Describe a task you completed from start to finish.
-    lookingFor:
-      - Follow-through
-      - Basic accountability
-    expectedDurationMinutes: 5
-developing:
-  - id: own_dev_1
-    text: Tell me about a time when you took responsibility for a mistake.
-    lookingFor:
-      - Accountability
-      - Learning from errors
-    expectedDurationMinutes: 5
-practicing:
-  - id: own_pract_1
-    text:
-      Describe a project where you owned the entire lifecycle from design to
-      production support.
-    lookingFor:
-      - End-to-end ownership
-      - Operational responsibility
-    expectedDurationMinutes: 8
-role_modeling:
-  - id: own_role_1
-    text: How do you build a culture of ownership in your team?
-    lookingFor:
-      - Team accountability
-      - Systemic approaches
-    expectedDurationMinutes: 8
-exemplifying:
-  - id: own_exemp_1
-    text:
-      How do you establish and drive ownership culture across an entire
-      organization?
-    followUps:
-      - How do you balance ownership with collaboration?
-    lookingFor:
-      - Enterprise ownership culture
-      - Accountability at scale
-    expectedDurationMinutes: 10
-  - id: own_exemp_2
-    text:
-      How do you hold yourself and others accountable for outcomes at an
-      organizational level?
-    lookingFor:
-      - Executive-level accountability
-      - Systemic ownership practices
-    expectedDurationMinutes: 10
+professionalQuestions:
+  emerging:
+    - id: own_pro_emerg_1
+      text:
+        A feature you built last week is causing intermittent errors in
+        production. Your tech lead is in a meeting and unavailable for an hour.
+      context:
+        The errors affect about 5% of users and the on-call engineer has pinged
+        the team channel. You have access to logs and the deployment pipeline.
+        The feature was built using AI-generated code that you reviewed before
+        merging.
+      simulationPrompts:
+        - Walk me through your first steps when you see the alert
+        - How would you decide whether to roll back or investigate further?
+        - Who would you communicate with and what would you say?
+        - How would you document what happened for the team?
+      lookingFor:
+        - Takes immediate responsibility rather than waiting for direction
+        - Shows willingness to act within their capability
+        - Communicates status proactively even without being asked
+        - Understands the feature serves a business purpose beyond code
+      expectedDurationMinutes: 20
+
+  developing:
+    - id: own_pro_dev_1
+      text:
+        You shipped a feature using AI-generated code that passed all tests, but
+        a stakeholder reports it behaves differently than specified.
+      context:
+        The stakeholder is frustrated because they demoed the feature to a
+        client and it didn't work as expected. The AI tool generated a plausible
+        but subtly wrong implementation that your tests didn't catch.
+      simulationPrompts:
+        - How do you respond to the stakeholder's frustration?
+        - What do you do to understand the gap between spec and implementation?
+        - How do you decide between a quick patch and a proper fix?
+        - What would you change about your review process going forward?
+      lookingFor:
+        - Takes ownership of the gap rather than blaming the AI tool
+        - Reviews AI-generated code critically against the specification
+        - Makes pragmatic trade-offs between speed and correctness
+        - Considers how to prevent similar gaps in future
+      expectedDurationMinutes: 20
+
+  practicing:
+    - id: own_pro_pract_1
+      text:
+        A key integration your team owns is blocking a partner team's quarterly
+        release. The fix requires accepting significant technical debt.
+      context:
+        The partner team's release is worth £2M in annual revenue. A proper fix
+        would take 3 weeks; a pragmatic workaround takes 3 days but leaves known
+        limitations. You own the stakeholder relationship with the partner
+        team's lead.
+      simulationPrompts:
+        - How do you evaluate the trade-off between technical debt and business
+          value?
+        - Walk me through the conversation you'd have with the partner team lead
+        - How do you ensure the technical debt is tracked and eventually
+          addressed?
+        - How do you communicate the decision and its consequences to your team?
+      lookingFor:
+        - Owns the end-to-end business outcome, not just the code
+        - Accepts technical debt intentionally with clear reasoning
+        - Manages the stakeholder relationship with transparency
+        - Balances delivery speed with long-term quality
+      expectedDurationMinutes: 20
+
+  role_modeling:
+    - id: own_pro_role_1
+      text:
+        Two teams in your function disagree about who owns a cross-cutting
+        reliability issue. Incidents are recurring and both teams blame the
+        other.
+      context:
+        The issue has caused 3 incidents this month, each impacting customer
+        experience. Neither team has full visibility into the other's service.
+        You are a senior IC with credibility with both teams. Leadership is
+        starting to notice.
+      simulationPrompts:
+        - How do you approach the situation without formal authority?
+        - What would you do to establish clear ownership boundaries?
+        - How do you shift the conversation from blame to accountability?
+        - What systemic changes would you propose to prevent this pattern?
+      lookingFor:
+        - Drives accountability culture focused on outcomes not blame
+        - Takes ownership of the problem without formal responsibility
+        - Makes decisions without needing to escalate for permission
+        - Establishes verification rigor for cross-team boundaries
+      expectedDurationMinutes: 20
+
+  exemplifying:
+    - id: own_pro_exemp_1
+      text:
+        The organisation is adopting AI code generation at scale, but there is
+        no accountability framework for AI-generated code quality and outcomes.
+      context:
+        Several teams have shipped AI-generated features with defects not caught
+        in review. Leadership wants velocity but also accountability. You have
+        been asked to define the organizational approach.
+      simulationPrompts:
+        - How do you define accountability standards for AI-generated code?
+        - How do you balance velocity gains from AI with outcome ownership?
+        - What organizational structures would you put in place?
+        - How would you measure success of the accountability framework?
+      lookingFor:
+        - Defines organizational accountability standards for the AI era
+        - Shapes practices that scale beyond individual team behaviour
+        - Sponsors initiatives with full outcome accountability
+        - Takes an approach that could influence industry practices
+      expectedDurationMinutes: 20
+      followUps:
+        - How would you handle a team that resists the framework?
+
+managementQuestions:
+  emerging:
+    - id: own_mgmt_emerg_1
+      text:
+        A team member's task is overdue and they haven't raised it. You discover
+        this during standup where they say everything is "on track."
+      context:
+        The task was due yesterday and blocks another team member's work. The
+        team member is relatively new and you suspect they may be struggling but
+        don't want to appear incompetent. The sprint goal is at risk.
+      simulationPrompts:
+        - How do you address this in the moment without embarrassing them?
+        - What conversation do you have with them privately afterwards?
+        - How do you ensure the blocking dependency is resolved?
+        - What do you put in place to catch this earlier next time?
+      lookingFor:
+        - Ensures follow-through on delegated tasks
+        - Creates psychological safety while maintaining accountability
+        - Addresses both the immediate blocker and the underlying pattern
+        - Shows awareness of team accountability dynamics
+      expectedDurationMinutes: 20
+
+  developing:
+    - id: own_mgmt_dev_1
+      text:
+        A team member shipped code that caused a production incident. During the
+        post-mortem, other team members want to assign blame.
+      context:
+        The incident affected 200 users for 45 minutes. The code was reviewed
+        and approved by another team member before merge. The author is junior
+        and clearly upset. Your team has no established incident ownership
+        culture.
+      simulationPrompts:
+        - How do you run the post-mortem to keep it constructive?
+        - How do you coach the team member privately afterwards?
+        - What do you say to the team about shared accountability?
+        - How do you start building an ownership culture from this moment?
+      lookingFor:
+        - Creates safe space for ownership while addressing the incident
+        - Coaches individual accountability constructively
+        - Models shared ownership rather than individual blame
+        - Begins establishing team accountability patterns
+      expectedDurationMinutes: 20
+
+  practicing:
+    - id: own_mgmt_pract_1
+      text:
+        Your team consistently treats operational issues as "someone else's
+        problem" once features ship. The platform team is overwhelmed.
+      context:
+        Your team shipped 12 features this quarter with strong velocity, but
+        operational tickets have doubled. The platform team lead has escalated
+        to your manager. Your team sees themselves as "builders, not operators."
+      simulationPrompts:
+        - How do you shift the team from feature delivery to outcome ownership?
+        - What structural changes embed operational ownership?
+        - How do you have the conversation with the platform team lead?
+        - How do you measure and recognize end-to-end ownership?
+      lookingFor:
+        - Structures team around end-to-end ownership, not just features
+        - Balances autonomy with accountability for operational outcomes
+        - Builds clear ownership expectations with concrete mechanisms
+        - Takes responsibility for the team culture gap
+      expectedDurationMinutes: 20
+
+  role_modeling:
+    - id: own_mgmt_role_1
+      text:
+        A project you championed has missed its business targets after 6 months.
+        Technology works but adoption is far lower than projected.
+      context:
+        You estimated £500K in annual savings but actual savings are £120K.
+        Technical delivery was on time and on budget. The adoption gap is due to
+        change management issues outside your initial scope. Your peers are
+        distancing themselves from the project.
+      simulationPrompts:
+        - How do you own this outcome publicly with leadership?
+        - What do you do about the adoption gap specifically?
+        - How do you model accountability when the outcome isn't what you
+          projected?
+        - What would you do differently if starting again?
+      lookingFor:
+        - Models personal accountability publicly, including for indirect
+          outcomes
+        - Owns the business outcome, not just the technical delivery
+        - Takes action to close the gap rather than accepting current state
+        - Shows transparency about lessons learned
+      expectedDurationMinutes: 20
+
+  exemplifying:
+    - id: own_mgmt_exemp_1
+      text:
+        You need to establish ownership expectations across a function where
+        teams have very different accountability cultures.
+      context:
+        You lead a function of 8 teams (60+ engineers). Three teams have strong
+        ownership cultures, three are inconsistent, and two actively avoid
+        accountability. Recent reorgs mixed people from different cultures and
+        cross-team incidents are increasing.
+      simulationPrompts:
+        - How do you assess ownership maturity across teams?
+        - What organizational standards would you establish?
+        - How do you bring lower-performing teams up without bureaucracy?
+        - How do you handle managers who resist accountability expectations?
+      lookingFor:
+        - Establishes organizational accountability standards
+        - Takes a systemic approach rather than team-by-team fixing
+        - Balances accountability with psychological safety at scale
+        - Creates sustainable culture that survives personnel changes
+      expectedDurationMinutes: 20
+      followUps:
+        - How would you measure the impact of the ownership culture change?