@forwardimpact/map 0.11.0

package/examples/self-assessments.yaml

@@ -0,0 +1,64 @@
+# yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/self-assessments.schema.json
+
+- id: example_mid_swe
+  skillLevels:
+    architecture_design: working
+    code_quality: working
+    devops: foundational
+    ai_augmented_development: foundational
+    technical_debt_management: foundational
+    lean_thinking: awareness
+    data_modeling: awareness
+    stakeholder_management: awareness
+    technical_writing: foundational
+    ai_literacy: foundational
+    service_management: awareness
+  behaviourMaturities:
+    precise_communication: developing
+    relentless_curiosity: developing
+    outcome_ownership: developing
+    polymathic_knowledge: emerging
+    systems_thinking: developing
+
+# Example: Senior Data Engineer
+- id: example_senior_de
+  skillLevels:
+    data_modeling: practitioner
+    data_integration: practitioner
+    architecture_design: working
+    code_quality: working
+    devops: working
+    cloud_platforms: working
+    ai_literacy: working
+    stakeholder_management: foundational
+    technical_writing: foundational
+    ai_augmented_development: foundational
+    lean_thinking: foundational
+  behaviourMaturities:
+    precise_communication: practicing
+    relentless_curiosity: practicing
+    outcome_ownership: practicing
+    polymathic_knowledge: developing
+    systems_thinking: practicing
+
+# Example: Data Scientist - R&D Focus
+- id: example_ds_rd
+  skillLevels:
+    model_development: working
+    data_analysis: working
+    statistical_modeling: working
+    data_modeling: foundational
+    ai_evaluation: working
+    technical_writing: foundational
+    business_immersion: foundational
+    code_quality: foundational
+    stakeholder_management: awareness
+    ai_literacy: working
+    multi_audience_communication: foundational
+    service_management: awareness
+  behaviourMaturities:
+    precise_communication: developing
+    relentless_curiosity: practicing
+    outcome_ownership: developing
+    polymathic_knowledge: developing
+    systems_thinking: developing

package/examples/stages.yaml

@@ -0,0 +1,191 @@
+# yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/stages.schema.json
+
+- id: specify
+  name: Specify
+  emojiIcon: "🎯"
+  summary: Defines requirements, user stories, and acceptance criteria
+  description:
+    Your primary task is to define WHAT users need and WHY, not how to build it.
+    Gather requirements, write user stories, and define acceptance criteria.
+  handoffs:
+    - targetStage: specify
+      label: Refine Spec
+      prompt: Refine spec.md with more detail or clarity.
+    - targetStage: specify
+      label: Alternative Spec
+      prompt: Create an alternative spec.md exploring a different approach.
+    - targetStage: plan
+      label: Create Plan
+      prompt: Create plan.md based on spec.md.
+  constraints:
+    - Do not write implementation code or execute system commands
+    - Focus on WHAT users need and WHY, not HOW to implement
+    - Write specifications as markdown files under specs/[feature-name]/spec.md
+    - Before writing the spec, conduct an interactive Q&A session with the user
+    - Ask each critical question one at a time and WAIT for answers
+    - You MUST ask questions interactively — do NOT embed unanswered questions
+    - Only after the user has answered your critical questions should you write
+      the spec document
+    - No technology choices, APIs, or code structure in specifications
+  readChecklist: []
+  confirmChecklist:
+    - spec.md exists with user stories and acceptance criteria
+    - No unresolved or open questions in spec.md
+
+- id: plan
+  name: Plan
+  emojiIcon: "📐"
+  summary: Designs architecture, makes technology choices, and defines contracts
+  description:
+    Your primary task is to define HOW to build the solution. Make technology
+    choices, design architecture, define contracts and data models.
+  handoffs:
+    - targetStage: plan
+      label: Refine Plan
+      prompt: Refine plan.md with more detail or clarity.
+    - targetStage: plan
+      label: Alternative Plan
+      prompt: Create an alternative plan.md exploring a different approach.
+    - targetStage: onboard
+      label: Set Up Environment
+      prompt: Prepare the development environment based on plan.md requirements.
+  constraints:
+    - Do not write implementation code or execute system commands
+    - Every technology choice must trace back to a specific requirement
+    - Write plans as markdown files under specs/[feature-name]/plan.md
+    - Define contracts and data models before implementation details
+    - Document rationale for architectural decisions
+  readChecklist: []
+  confirmChecklist:
+    - spec.md exists with user stories and acceptance criteria
+    - No unresolved or open questions in spec.md
+    - plan.md exists with technology choices and architecture
+    - Contracts and data models defined where applicable
+    - No unresolved or open questions in plan.md
+
+- id: onboard
+  name: Onboard
+  emojiIcon: "🔧"
+  summary:
+    Prepares the development environment with dependencies, tools, and
+    credentials
+  description:
+    Your primary task is to prepare the development environment with all
+    prerequisites for coding. Install dependencies, configure tools, set up
+    credentials, and verify the environment is ready for implementation.
+  handoffs:
+    - targetStage: onboard
+      label: Retry Setup
+      prompt: Re-run the environment setup to fix remaining issues.
+    - targetStage: plan
+      label: Update Plan
+      prompt: Update plan.md because the environment setup revealed issues.
+    - targetStage: code
+      label: Start Coding
+      prompt: Implement the tasks defined in plan.md.
+  constraints:
+    - Do not implement feature code; focus only on environment setup
+    - Verify each tool and dependency works before moving on
+    - Document all environment configuration in a reproducible way
+    - Never hardcode secrets; use .env files or secret managers
+    - Track progress with the todo tool
+  readChecklist: []
+  confirmChecklist:
+    - plan.md exists with technology choices and architecture
+    - No unresolved or open questions in plan.md
+    - Install scripts (scripts/install.sh) executed for all skills that provide
+      them
+    - All dependencies installed and versions verified
+    - Environment variables and secrets configured (.env files, tokens)
+    - Linter and formatter configured and passing on existing code
+    - Build and test commands run successfully
+    - Version control hooks and CI checks are operational
+    - Development server or runtime starts without errors
+
+- id: code
+  name: Code
+  emojiIcon: "💻"
+  summary: Implements solutions, writes tests, and iterates to completion
+  description:
+    Your primary task is to implement the solution. Write code, write tests, and
+    iterate until the implementation is complete.
+  handoffs:
+    - targetStage: review
+      label: Request Review
+      prompt: Review the implemented changes.
+  constraints:
+    - Implement one task at a time, verify before moving on
+    - Write tests alongside implementation
+    - Track progress with the todo tool
+  readChecklist: []
+  confirmChecklist:
+    - spec.md exists with user stories and acceptance criteria
+    - plan.md exists with technology choices and architecture
+    - No unresolved [NEEDS CLARIFICATION] markers in plan.md
+    - All dependencies installed and versions verified
+    - Linter and formatter configured and passing
+    - Build and test commands run successfully
+    - Implementation complete according to plan.md
+    - Tests written and passing
+    - Self-review completed
+
+- id: review
+  name: Review
+  emojiIcon: "🔍"
+  summary:
+    Verifies implementation, tests acceptance criteria, and documents findings
+  description:
+    Your primary task is to verify the implementation works correctly. Run the
+    application, test against acceptance criteria, document findings.
+  handoffs:
+    - targetStage: code
+      label: Request Changes
+      prompt: Address the findings in review.md.
+    - targetStage: plan
+      label: Needs Re-planning
+      prompt: Update plan.md to address issues found in review.md.
+    - targetStage: deploy
+      label: Deploy
+      prompt: Deploy the approved changes.
+  constraints:
+    - Do not make code edits
+    - Write review findings as markdown under specs/[feature-name]/review.md
+    - Prioritize actionable feedback over exhaustive lists
+    - Track findings and required changes with the todo tool
+    - Run the application locally and verify changes work as expected
+    - Test user-facing functionality against acceptance criteria
+  readChecklist: []
+  confirmChecklist:
+    - Implementation complete according to plan.md
+    - Tests written and passing
+    - Self-review completed
+    - Application runs locally without errors
+    - Changes verified against acceptance criteria through manual testing
+    - No blocking issues identified in review
+    - Review approved
+
+- id: deploy
+  name: Deploy
+  emojiIcon: "🚀"
+  summary: Ships changes to production and monitors deployment workflows
+  description:
+    Your primary task is to ship the changes to production. Push code, monitor
+    CI/CD workflows, and verify successful deployment.
+  handoffs:
+    - targetStage: code
+      label: Fix Pipeline
+      prompt: Fix the failing workflow issues identified during deployment.
+  constraints:
+    - Use git push to deploy changes
+    - Use gh CLI to monitor triggered workflows (gh run list, gh run watch)
+    - Do not make code edits; hand off to code stage if fixes are needed
+    - Verify all workflows complete successfully before considering deployment
+      done
+  readChecklist: []
+  confirmChecklist:
+    - Application runs locally without errors
+    - Changes verified against acceptance criteria through manual testing
+    - No blocking issues identified in review
+    - Review approved
+    - All triggered workflows are green
+    - Deployment verified in target environment

package/examples/tracks/_index.yaml

@@ -0,0 +1,5 @@
+# Auto-generated index for browser loading
+# Do not edit manually - regenerate with: npx pathway --generate-index
+files:
+  - platform
+  - sre

package/examples/tracks/platform.yaml

@@ -0,0 +1,47 @@
+# yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/track.schema.json
+
+name: Platform
+
+# Shared content (used by both human job descriptions and agent profiles)
+description:
+  Internal tooling and infrastructure focus, building shared capabilities that
+  enable other engineering teams. Treats the platform as a product with
+  developers as customers.
+roleContext:
+  In this platform-focused role, you will build internal tooling and shared
+  infrastructure that enables other engineering teams to be more productive. You
+  will treat the platform as a product—conducting user research, building golden
+  paths, and optimizing for developer experience.
+
+# Derivation inputs - used by both human and agent profiles
+skillModifiers:
+  delivery: 1
+  business: 1
+  reliability: -1
+behaviourModifiers:
+  systems_thinking: 1
+  precise_communication: 1
+assessmentWeights:
+  skillWeight: 0.6
+  behaviourWeight: 0.4
+
+# Agent-specific content
+agent:
+  identity: |
+    You are a Platform {roleTitle} agent. Your primary focus is
+    building self-service capabilities that enable other engineers.
+    You treat checklists the way surgeons and pilots do—not as a
+    crutch, but as a discipline that catches the errors expertise
+    alone cannot prevent.
+  priority: |
+    Developer experience is paramount. You design golden paths, maintain 
+    backward compatibility, and document everything. Code quality and 
+    architecture matter because your consumers depend on your stability.
+
+    Every API change must consider developer experience. Treat breaking 
+    changes with extreme caution—your consumers build on your stability.
+  constraints:
+    - Maintain backward compatibility
+    - Document breaking changes with migration guides
+    - Test all changes against real consumer use cases
+    - Design for Day 50, not just Day 1

package/examples/tracks/sre.yaml

@@ -0,0 +1,46 @@
+# yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/track.schema.json
+
+name: SRE
+
+# Shared content (used by both human job descriptions and agent profiles)
+description:
+  Site Reliability Engineering focus on system reliability, observability, and
+  incident response
+roleContext:
+  In this Site Reliability Engineering role, you will focus on system
+  reliability, observability, and incident response. You will ensure our
+  services meet their reliability targets while driving continuous improvement
+  in system resilience and operational excellence.
+
+# Derivation inputs - used by both human and agent profiles
+skillModifiers:
+  scale: 1
+  reliability: 1
+  delivery: -1
+behaviourModifiers:
+  outcome_ownership: 1
+  relentless_curiosity: 1
+assessmentWeights:
+  skillWeight: 0.6
+  behaviourWeight: 0.4
+
+# Agent-specific content
+agent:
+  identity: |
+    You are an SRE {roleTitle} agent. Your primary focus is
+    system reliability, observability, and incident response. You
+    treat checklists the way surgeons and pilots do—not as a crutch,
+    but as a discipline that catches the errors expertise alone
+    cannot prevent.
+  priority: |
+    Reliability is non-negotiable. You instrument everything, design for 
+    graceful degradation, and maintain error budgets. Every change 
+    considers blast radius and recovery paths.
+
+    Production stability trumps feature velocity. No change ships without
+    understanding its impact on system reliability.
+  constraints:
+    - Never compromise on observability instrumentation
+    - Document all runbooks and incident response procedures
+    - Verify failover mechanisms regularly
+    - Consider blast radius for all changes

package/examples/vscode-settings.yaml

@@ -0,0 +1,21 @@
+# Enable coding agent
+chat.agent.enabled: true
+
+# Maximum requests per agent session (high limit for complex tasks)
+chat.agent.maxRequests: 999
+
+# Enable edits v2 for improved code editing
+chat.edits2.enabled: true
+
+# Enable extension unification for consistent behavior
+chat.extensionUnification.enabled: true
+
+# Enable custom agents to be used as subagents
+# Required for multi-agent workflows with handoffs
+chat.customAgentInSubagent.enabled: true
+
+# Enable agent skills for enhanced agent capabilities
+chat.useAgentSkills: true
+
+# Enable skill adherence prompt to improve agent compliance with defined skills
+chat.experimental.useSkillAdherencePrompt: true

package/package.json

@@ -0,0 +1,49 @@
+{
+  "name": "@forwardimpact/map",
+  "version": "0.11.0",
+  "description": "Public data model for career frameworks, consumed by AI agents and engineers",
+  "license": "Apache-2.0",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/forwardimpact/monorepo",
+    "directory": "products/map"
+  },
+  "homepage": "https://www.forwardimpact.team/map",
+  "type": "module",
+  "main": "src/index.js",
+  "bin": {
+    "fit-map": "./bin/fit-map.js"
+  },
+  "scripts": {
+    "generate-index": "node ./bin/fit-map.js generate-index",
+    "validate": "node ./bin/fit-map.js validate"
+  },
+  "files": [
+    "bin/",
+    "examples/",
+    "src/",
+    "schema/"
+  ],
+  "exports": {
+    ".": "./src/index.js",
+    "./loader": "./src/loader.js",
+    "./validation": "./src/validation.js",
+    "./schema-validation": "./src/schema-validation.js",
+    "./index-generator": "./src/index-generator.js",
+    "./levels": "./src/levels.js",
+    "./examples/*": "./examples/*",
+    "./schema/json/*": "./schema/json/*",
+    "./schema/rdf/*": "./schema/rdf/*"
+  },
+  "dependencies": {
+    "ajv": "^8.17.1",
+    "ajv-formats": "^3.0.1",
+    "yaml": "^2.3.4"
+  },
+  "devDependencies": {
+    "n3": "^2.0.1"
+  },
+  "engines": {
+    "node": ">=18.0.0"
+  }
+}

package/schema/json/behaviour-questions.schema.json

@@ -0,0 +1,95 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "$id": "https://www.forwardimpact.team/schema/json/behaviour-questions.schema.json",
+  "title": "Behaviour Interview Questions",
+  "description": "Stakeholder simulation interview questions for a behaviour, organized by role type (professional/management) and maturity level. Each question presents a realistic stakeholder scenario to assess behavioural maturity.",
+  "type": "object",
+  "properties": {
+    "professionalQuestions": {
+      "description": "Questions for professional/IC roles (e.g., engineers)",
+      "$ref": "#/$defs/maturityQuestions"
+    },
+    "managementQuestions": {
+      "description": "Questions for management roles (e.g., engineering managers, product managers)",
+      "$ref": "#/$defs/maturityQuestions"
+    }
+  },
+  "additionalProperties": false,
+  "$defs": {
+    "maturityQuestions": {
+      "type": "object",
+      "description": "Questions organized by behaviour maturity level",
+      "properties": {
+        "emerging": {
+          "type": "array",
+          "items": { "$ref": "#/$defs/question" }
+        },
+        "developing": {
+          "type": "array",
+          "items": { "$ref": "#/$defs/question" }
+        },
+        "practicing": {
+          "type": "array",
+          "items": { "$ref": "#/$defs/question" }
+        },
+        "role_modeling": {
+          "type": "array",
+          "items": { "$ref": "#/$defs/question" }
+        },
+        "exemplifying": {
+          "type": "array",
+          "items": { "$ref": "#/$defs/question" }
+        }
+      },
+      "additionalProperties": false
+    },
+    "question": {
+      "type": "object",
+      "required": ["id", "text", "lookingFor", "simulationPrompts"],
+      "properties": {
+        "id": {
+          "type": "string",
+          "pattern": "^[a-z][a-z0-9_]*$",
+          "description": "Unique question identifier (format: {abbrev}_{maturity_abbrev}_{number})"
+        },
+        "text": {
+          "type": "string",
+          "maxLength": 300,
+          "description": "The stakeholder scenario (second person, sets up a realistic situation)"
+        },
+        "context": {
+          "type": "string",
+          "description": "Additional context to set up the simulation scenario"
+        },
+        "simulationPrompts": {
+          "type": "array",
+          "description": "3-5 guiding prompts to steer the simulation and probe the candidate's behaviour",
+          "minItems": 2,
+          "maxItems": 5,
+          "items": { "type": "string" }
+        },
+        "lookingFor": {
+          "type": "array",
+          "description": "2-4 indicators of strong behavioural response",
+          "minItems": 2,
+          "maxItems": 4,
+          "items": { "type": "string" }
+        },
+        "expectedDurationMinutes": {
+          "type": "integer",
+          "minimum": 10,
+          "default": 20,
+          "description": "Expected duration in minutes (default: 20 for stakeholder simulation)"
+        },
+        "followUps": {
+          "type": "array",
+          "description": "1-3 probing questions for deeper exploration",
+          "minItems": 1,
+          "maxItems": 3,
+          "items": { "type": "string" }
+        }
+      },
+      "additionalProperties": false
+    }
+  }
+}

package/schema/json/behaviour.schema.json

@@ -0,0 +1,73 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "$id": "https://www.forwardimpact.team/schema/json/behaviour.schema.json",
+  "title": "Behaviour",
+  "description": "Mindset and way of working that underpins effective application of skills",
+  "type": "object",
+  "required": ["name", "human"],
+  "properties": {
+    "name": {
+      "type": "string",
+      "description": "Human-readable behaviour name"
+    },
+    "human": {
+      "$ref": "#/$defs/behaviourHumanSection",
+      "description": "Human-specific content"
+    },
+    "agent": {
+      "$ref": "#/$defs/behaviourAgentSection",
+      "description": "Agent-specific content"
+    }
+  },
+  "additionalProperties": false,
+  "$defs": {
+    "behaviourHumanSection": {
+      "type": "object",
+      "required": ["description", "maturityDescriptions"],
+      "properties": {
+        "description": {
+          "type": "string",
+          "description": "Description of the behaviour"
+        },
+        "maturityDescriptions": {
+          "$ref": "#/$defs/maturityDescriptions",
+          "description": "Description of expectations at each maturity level"
+        }
+      },
+      "additionalProperties": false
+    },
+    "maturityDescriptions": {
+      "type": "object",
+      "properties": {
+        "emerging": { "type": "string" },
+        "developing": { "type": "string" },
+        "practicing": { "type": "string" },
+        "role_modeling": { "type": "string" },
+        "exemplifying": { "type": "string" }
+      },
+      "required": [
+        "emerging",
+        "developing",
+        "practicing",
+        "role_modeling",
+        "exemplifying"
+      ],
+      "additionalProperties": false
+    },
+    "behaviourAgentSection": {
+      "type": "object",
+      "required": ["title", "workingStyle"],
+      "properties": {
+        "title": {
+          "type": "string",
+          "description": "Short title for the behaviour's agent application"
+        },
+        "workingStyle": {
+          "type": "string",
+          "description": "How the agent should apply this behaviour"
+        }
+      },
+      "additionalProperties": false
+    }
+  }
+}