@forwardimpact/map 0.11.1 → 0.13.0

package/examples/copilot-setup-steps.yaml

@@ -1,25 +0,0 @@
-# Copilot Coding Agent setup steps workflow
-# This workflow is executed when a Copilot Coding Agent starts
-# to prepare the environment for the agent session.
-#
-# Reference: https://docs.github.com/en/copilot/customizing-copilot/customizing-the-development-environment-for-copilot-coding-agent
-
-name: Copilot Setup Steps
-
-on: copilot_setup_steps
-
-jobs:
-  setup:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: "22"
-          cache: npm
-
-      - name: Install dependencies
-        run: npm ci

package/examples/devcontainer.yaml

@@ -1,21 +0,0 @@
-# Dev Container configuration template
-# Settings are dynamically populated at generation time
-
-# Base image for Node.js development
-image: mcr.microsoft.com/devcontainers/javascript-node:22-bookworm
-
-# VS Code customizations are populated dynamically from vscode-settings.yaml
-# customizations:
-#   vscode:
-#     settings: { ... dynamically injected ... }
-
-# Features to add to the dev container
-features:
-  ghcr.io/devcontainers/features/github-cli:1: {}
-
-# Lifecycle commands
-postCreateCommand: npm install
-
-# Forward ports from the container (e.g., for dev server)
-forwardPorts:
-  - 3000

package/examples/disciplines/_index.yaml

@@ -1,6 +0,0 @@
-# Auto-generated index for browser loading
-# Do not edit manually - regenerate with: npx pathway --generate-index
-files:
-  - data_engineering
-  - engineering_management
-  - software_engineering

package/examples/disciplines/data_engineering.yaml

@@ -1,68 +0,0 @@
-# yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/discipline.schema.json
-
-specialization: Data Engineering
-roleTitle: Data Engineer
-isProfessional: true
-# null = allow trackless (generalist)
-validTracks:
-  - null
-  - platform
-  - sre
-
-# Shared content (human and agent)
-description:
-  Designs and builds data integration, storage systems, and data infrastructure
-  to enable analytics and AI. Masters the art of gaining access to enterprise
-  data and making it usable.
-
-# Derivation inputs
-coreSkills:
-  - data_modeling
-  - architecture_design
-  - cloud_platforms
-supportingSkills:
-  - code_quality
-  - full_stack_development
-  - devops
-  - sre_practices
-broadSkills:
-  - stakeholder_management
-  - technical_writing
-  - team_collaboration
-behaviourModifiers:
-  systems_thinking: 1
-  outcome_ownership: 1
-  relentless_curiosity: 1
-
-# Human-specific content
-human:
-  professionalRoleSummary:
-    We are seeking a skilled {roleTitle} who will design and build data
-    integration, storage systems, and data infrastructure that enable analytics
-    and AI capabilities. In this role, you will master the art of gaining access
-    to enterprise data and making it usable for decision-making across the
-    organization.
-  managementRoleSummary:
-    We are seeking an experienced {specialization} leader to build and lead
-    high-performing data engineering teams. In this role, you will drive the
-    strategic direction of our data infrastructure while developing talent and
-    ensuring data capabilities meet business needs. You will champion data
-    quality, governance, and the democratization of data across the
-    organization.
-
-# Agent-specific content
-agent:
-  identity: |
-    You are a {roleTitle} agent. Your focus is designing and building
-    data integration, storage systems, and data infrastructure that
-    enables analytics and AI capabilities. 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: |
-    Data quality is paramount. Always validate data at ingestion points and
-    document schema assumptions. Treat undocumented schemas with suspicion.
-  constraints:
-    - Ignoring data quality issues
-    - Creating pipelines without proper error handling
-    - Undocumented schema changes
-    - Tight coupling between data producers and consumers

package/examples/disciplines/engineering_management.yaml

@@ -1,61 +0,0 @@
-# yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/discipline.schema.json
-
-specialization: Engineering Management
-roleTitle: Engineering Manager
-isManagement: true
-minLevel: L2
-
-description: |
-  People and delivery leadership, focusing on team effectiveness,
-  career development, and organizational outcomes.
-
-# null = allow trackless (generalist)
-validTracks:
-  - null
-
-coreSkills:
-  - stakeholder_management
-  - team_collaboration
-supportingSkills:
-  - code_quality
-  - devops
-broadSkills:
-  - architecture_design
-  - technical_writing
-
-behaviourModifiers:
-  outcome_ownership: 1
-  systems_thinking: 1
-
-# Human-specific content
-human:
-  professionalRoleSummary:
-    We are seeking a skilled {roleTitle} who will lead engineering teams,
-    focusing on team effectiveness, career development, and organizational
-    outcomes. In this role, you will create space for curiosity and
-    experimentation while modeling ownership behaviours.
-  managementRoleSummary:
-    We are seeking an experienced {specialization} leader to build and lead
-    high-performing engineering teams. In this role, you will drive team
-    effectiveness and career development while ensuring organizational outcomes
-    are achieved. You will create space for innovation and model the ownership
-    behaviors that define our engineering culture.
-
-# Agent-specific content
-agent:
-  identity: |
-    You are an {specialization} leadership support agent. Your primary
-    focus is supporting engineering managers with team effectiveness,
-    process design, and communication. 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: |
-    People and process over direct implementation. You help create space 
-    for curiosity and experimentation, model ownership behaviors, and 
-    remove organizational friction.
-
-    Your role is to support engineering judgment, not replace it.
-  constraints:
-    - Focus on enabling and empowering rather than doing directly
-    - Consider long-term team health over short-term fixes
-    - Support engineering judgment, don't replace it

package/examples/disciplines/software_engineering.yaml

@@ -1,68 +0,0 @@
-# yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/discipline.schema.json
-
-specialization: Software Engineering
-roleTitle: Software Engineer
-isProfessional: true
-# null = allow trackless (generalist)
-validTracks:
-  - null
-  - platform
-  - sre
-
-# Shared content (human and agent)
-description:
-  Builds and maintains software systems, focusing on code quality, architecture,
-  and reliable delivery of business value. In the AI era, emphasizes
-  verification and review of AI-generated code.
-
-# Derivation inputs
-coreSkills:
-  - architecture_design
-  - code_quality
-  - full_stack_development
-supportingSkills:
-  - devops
-  - cloud_platforms
-  - sre_practices
-broadSkills:
-  - data_modeling
-  - stakeholder_management
-  - technical_writing
-  - team_collaboration
-behaviourModifiers:
-  outcome_ownership: 1
-  systems_thinking: 1
-  relentless_curiosity: 1
-
-# Human-specific content
-human:
-  professionalRoleSummary:
-    We are seeking a skilled {roleTitle} who will design, build, and maintain
-    software systems that deliver business value. In this role, you will focus
-    on code quality, architecture decisions, and reliable delivery while
-    leveraging AI tools to enhance productivity. You will verify and review
-    AI-generated code to ensure it meets our quality standards.
-  managementRoleSummary:
-    We are seeking an experienced {specialization} leader to build and lead
-    high-performing software engineering teams. In this role, you will drive
-    technical excellence while developing talent and ensuring delivery of
-    business value. You will set technical direction, create space for
-    innovation, and model the ownership behaviors that define our engineering
-    culture.
-
-# Agent-specific content
-agent:
-  identity: |
-    You are a {roleTitle} agent. Your primary focus is writing
-    correct, maintainable, well-tested code. 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: |
-    Code review is more important than code generation. Every line of code
-    you produce must be understood and verified. Never ship code without
-    comprehensive testing.
-  constraints:
-    - Committing code without running tests
-    - Making changes without understanding the existing codebase
-    - Ignoring error handling and edge cases
-    - Over-engineering simple solutions

package/examples/drivers.yaml

@@ -1,202 +0,0 @@
-# yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/drivers.schema.json
-
-- id: clear_direction
-  name: Clear Direction
-  description:
-    The degree to which developers understand their team's mission, goals, and
-    alignment with the greater organization
-  contributingSkills:
-    - stakeholder_management
-    - technical_writing
-  contributingBehaviours:
-    - polymathic_knowledge
-    - systems_thinking
-
-- id: say_on_priorities
-  name: Say on Priorities
-  description:
-    The involvement and influence developers hold in shaping their team's
-    direction and tasks
-  contributingSkills:
-    - stakeholder_management
-    - team_collaboration
-  contributingBehaviours:
-    - outcome_ownership
-    - relentless_curiosity
-
-- id: requirements_quality
-  name: Requirements Quality
-  description:
-    How well specifications are defined for tasks and projects, encompassing
-    completeness and stability of requirements
-  contributingSkills:
-    - stakeholder_management
-    - technical_writing
-    - architecture_design
-  contributingBehaviours:
-    - precise_communication
-    - systems_thinking
-
-# Delivery & Release
-- id: ease_of_release
-  name: Ease of Release
-  description:
-    The amount of friction involved in releasing code to end-users, encompassing
-    validation, packaging, and deployment
-  contributingSkills:
-    - devops
-    - code_quality
-    - full_stack_development
-    - cloud_platforms
-  contributingBehaviours:
-    - outcome_ownership
-    - precise_communication
-
-- id: test_efficiency
-  name: Test Efficiency
-  description:
-    The speed and stability of an automated test suite, affecting feedback loops
-    in the software development lifecycle
-  contributingSkills:
-    - full_stack_development
-    - code_quality
-    - devops
-  contributingBehaviours:
-    - outcome_ownership
-    - relentless_curiosity
-
-- id: managing_tech_debt
-  name: Managing Tech Debt
-  description:
-    Continuously identifying, analyzing, and addressing technical debt to
-    maintain developer productivity
-  contributingSkills:
-    - code_quality
-    - architecture_design
-  contributingBehaviours:
-    - outcome_ownership
-    - systems_thinking
-
-# Quality & Documentation
-- id: code_review
-  name: Code Review
-  description:
-    The timeliness and quality of feedback received during code review, as well
-    as the experience of reviewing others' code
-  contributingSkills:
-    - code_quality
-    - team_collaboration
-  contributingBehaviours:
-    - precise_communication
-    - relentless_curiosity
-
-- id: documentation
-  name: Documentation
-  description:
-    Helping developers obtain the information they need to understand and
-    complete technical tasks
-  contributingSkills:
-    - technical_writing
-  contributingBehaviours:
-    - precise_communication
-    - polymathic_knowledge
-
-- id: codebase_experience
-  name: Codebase Experience
-  description:
-    The ease of understanding and modifying code, significantly affecting
-    overall developer experience
-  contributingSkills:
-    - code_quality
-    - architecture_design
-  contributingBehaviours:
-    - relentless_curiosity
-    - polymathic_knowledge
-
-# Operations & Reliability
-- id: incident_response
-  name: Incident Response
-  description:
-    How developers handle and resolve issues in their systems, including triage,
-    resolution, and communication
-  contributingSkills:
-    - sre_practices
-    - devops
-    - cloud_platforms
-  contributingBehaviours:
-    - outcome_ownership
-    - systems_thinking
-
-# Learning & Growth
-- id: learning_culture
-  name: Learning Culture
-  description:
-    The team characteristic of continuously improving and learning from past
-    experience
-  contributingSkills:
-    - team_collaboration
-    - technical_writing
-  contributingBehaviours:
-    - relentless_curiosity
-    - polymathic_knowledge
-
-- id: experimentation
-  name: Experimentation
-  description:
-    Activities that generate new ideas, test hypotheses, and capture insights
-    from experiments
-  contributingSkills:
-    - data_modeling
-    - full_stack_development
-  contributingBehaviours:
-    - relentless_curiosity
-    - polymathic_knowledge
-
-# Team & Collaboration
-- id: connectedness
-  name: Connectedness
-  description:
-    The state of feeling linked and related to others at work, fostered through
-    communication and interaction
-  contributingSkills:
-    - team_collaboration
-    - stakeholder_management
-  contributingBehaviours:
-    - precise_communication
-    - polymathic_knowledge
-
-- id: efficient_processes
-  name: Efficient Processes
-  description:
-    How effectively team members collaborate to design and deliver software
-    using principles and workflows
-  contributingSkills:
-    - team_collaboration
-    - devops
-  contributingBehaviours:
-    - precise_communication
-    - outcome_ownership
-
-- id: deep_work
-  name: Deep Work
-  description:
-    The ability to focus on tasks without distraction, achieved by minimizing
-    interruptions and context switching
-  contributingSkills:
-    - architecture_design
-    - code_quality
-  contributingBehaviours:
-    - relentless_curiosity
-    - precise_communication
-
-# User Focus
-- id: leveraging_user_feedback
-  name: Leveraging User Feedback
-  description:
-    Collecting, analyzing, and taking action based on insights from end-users
-  contributingSkills:
-    - stakeholder_management
-    - data_modeling
-  contributingBehaviours:
-    - relentless_curiosity
-    - precise_communication

package/examples/framework.yaml

@@ -1,73 +0,0 @@
-# yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/framework.schema.json
-
-title: Engineering Pathway
-emojiIcon: "🧭"
-tag: "#AcmeCorp"
-description: |
-  Great engineering comes from improving the performance of people and machines together. The pathway defines skills, behaviours, and career levels that apply equally to human engineers and coding agent teams—raising quality, increasing output, and bringing pride of workmanship to both.
-
-# Distribution configuration
-distribution:
-  siteUrl: https://pathway.example.com
-
-# Entity definitions for pages and chapters
-entityDefinitions:
-  driver:
-    title: Drivers
-    emojiIcon: "🎯"
-    description: |
-      Organizational outcomes that productive teams achieve. Drivers link skills and behaviours to business value, helping teams understand how their capabilities contribute to organizational success.
-
-  skill:
-    title: Skills
-    emojiIcon: "💡"
-    description: |
-      Capabilities required to perform work effectively. Skills are organized by capability and measured across five levels from Awareness to Expert. They form the foundation of technical and professional competence.
-
-  behaviour:
-    title: Behaviours
-    emojiIcon: "🧠"
-    description: |
-      Mindsets and ways of working that underpin effective application of skills. Behaviours are measured across five maturity levels from Emerging to Exemplifying. They describe how engineers approach their work, collaborate with others, and drive outcomes.
-
-  discipline:
-    title: Disciplines
-    emojiIcon: "🔬"
-    description: |
-      Engineering specializations that define T-shaped skill profiles. Each discipline specifies primary skills for deep expertise, secondary skills for supporting capabilities, and broad skills for general awareness. Disciplines answer the question: "What kind of engineer are you?"
-
-  level:
-    title: Levels
-    emojiIcon: "📊"
-    description: |
-      Career levels that define expectations for skill proficiency, behaviour maturity, and scope of impact. Levels provide a clear progression path from entry-level to distinguished leadership roles, with defined expectations at each stage.
-
-  track:
-    title: Tracks
-    emojiIcon: "🛤️"
-    description: |
-      Work contexts that modify skill and behaviour expectations based on the nature of the role. Tracks answer the question: "Where and how do you work?" They apply modifiers to adjust expectations for different working environments and responsibilities.
-
-  job:
-    title: Jobs
-    emojiIcon: "📋"
-    description: |
-      Complete role specifications that combine discipline, track, and level into actionable job definitions with skill matrices, behaviour profiles, and derived responsibilities. Jobs represent the practical application of the framework to define concrete engineering positions.
-
-  agent:
-    title: Agents
-    emojiIcon: "🤖"
-    description: |
-      AI coding agent configurations generated from the same disciplines, tracks, and skills that define human roles. Agent profiles and skills follow the GitHub Copilot specification, ensuring AI assistants understand context, constraints, and working styles aligned with human engineering expectations.
-
-  stage:
-    title: Stages
-    emojiIcon: "🔄"
-    description: |
-      Defined phases of the engineering lifecycle that structure work from planning through delivery and review. Stages provide context for AI agents and define entry criteria, exit criteria, and appropriate handoffs between phases.
-
-  tool:
-    title: Tools
-    emojiIcon: "🔧"
-    description: |
-      Required tools and utilities referenced by skills for effective engineering workflows. Tools are linked to specific skills with guidance on when and how to use them, surfacing organizational standards directly in skill definitions.

package/examples/levels.yaml

@@ -1,115 +0,0 @@
-# yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/levels.schema.json
-
-- id: L1
-  professionalTitle: Engineer I
-  managementTitle: Associate Manager
-  typicalExperienceRange: "0-2"
-  ordinalRank: 1
-  qualificationSummary:
-    Entry-level position for those new to the field or transitioning careers.
-    Bachelor's degree or equivalent practical experience.
-  baseSkillProficiencies:
-    primary: foundational
-    secondary: awareness
-    broad: awareness
-  baseBehaviourMaturity: emerging
-  expectations:
-    impactScope:
-      Individual tasks and small features with guidance from senior team members
-    autonomyExpectation:
-      Work with close supervision and ask for help when encountering challenges
-    influenceScope:
-      Contribute to team discussions and learn from experienced colleagues
-    complexityHandled:
-      Standard tasks with established patterns and clear requirements
-
-- id: L2
-  professionalTitle: Engineer II
-  managementTitle: Manager
-  typicalExperienceRange: "2-5"
-  ordinalRank: 2
-  qualificationSummary: >
-    {typicalExperienceRange} years of relevant experience. Demonstrated ability
-    to complete tasks independently and contribute effectively to team projects.
-  baseSkillProficiencies:
-    primary: foundational
-    secondary: foundational
-    broad: awareness
-  baseBehaviourMaturity: emerging
-  expectations:
-    impactScope: Complete features and components delivered independently
-    autonomyExpectation:
-      Work independently on familiar problems while seeking guidance on novel
-      situations
-    influenceScope:
-      Help onboard new team members and participate actively in code reviews
-    complexityHandled: Moderate complexity with some ambiguity in requirements
-
-- id: L3
-  professionalTitle: Senior Engineer
-  managementTitle: Senior Manager
-  typicalExperienceRange: "5-8"
-  ordinalRank: 3
-  qualificationSummary: >
-    {typicalExperienceRange} years of relevant experience. Proven track record
-    of leading technical initiatives and mentoring team members.
-  baseSkillProficiencies:
-    primary: practitioner
-    secondary: working
-    broad: foundational
-  baseBehaviourMaturity: developing
-  expectations:
-    impactScope:
-      Large features and technical initiatives including leading small projects
-    autonomyExpectation:
-      Do self-directed work while seeking input on strategic decisions
-    influenceScope: Shape team practices and mentor junior engineers
-    complexityHandled: High complexity with comfort navigating ambiguity
-
-- id: L4
-  professionalTitle: Staff Engineer
-  managementTitle: Director
-  typicalExperienceRange: "8-12"
-  ordinalRank: 4
-  qualificationSummary: >
-    {typicalExperienceRange} years of relevant experience. Extensive experience
-    leading complex technical projects with multi-team impact.
-  baseSkillProficiencies:
-    primary: expert
-    secondary: practitioner
-    broad: working
-  baseBehaviourMaturity: practicing
-  breadthCriteria:
-    practitioner: 4
-  expectations:
-    impactScope: Multi-team initiatives with area-wide impact
-    autonomyExpectation: Set own direction within broader strategic goals
-    influenceScope:
-      Influence teams in your area and be recognized as a domain expert
-    complexityHandled:
-      Very high complexity driving through ambiguity to deliver results
-
-- id: L5
-  professionalTitle: Principal Engineer
-  managementTitle: VP of Engineering
-  typicalExperienceRange: "12+"
-  ordinalRank: 5
-  qualificationSummary: >
-    {typicalExperienceRange} years of relevant experience. Deep technical
-    expertise with a proven track record of organization-wide technical
-    leadership.
-  baseSkillProficiencies:
-    primary: expert
-    secondary: expert
-    broad: practitioner
-  baseBehaviourMaturity: role_modeling
-  breadthCriteria:
-    practitioner: 5
-    expert: 2
-  expectations:
-    impactScope: Business unit technical strategy and architectural direction
-    autonomyExpectation:
-      Define strategic direction and be accountable for outcomes
-    influenceScope:
-      Shape practices across the business unit and maintain external visibility
-    complexityHandled: Business unit complexity creating clarity from ambiguity