@forwardimpact/pathway 0.25.21 → 0.25.24

package/src/commands/init.js

@@ -1,64 +0,0 @@
-/**
- * Init Command
- *
- * Initializes a new Engineering Pathway project by copying starter data.
- */
-
-import { cp, access } from "fs/promises";
-import { join, dirname } from "path";
-import { fileURLToPath } from "url";
-
-const __dirname = dirname(fileURLToPath(import.meta.url));
-const starterDir = join(__dirname, "..", "..", "starter");
-
-/**
- * Run the init command
- * @param {Object} params - Command parameters
- * @param {Object} params.options - Command options
- */
-export async function runInitCommand({ options }) {
-  const targetPath = options.path || process.cwd();
-  const dataDir = join(targetPath, "data", "pathway");
-
-  // Check if data/pathway/ already exists
-  try {
-    await access(dataDir);
-    console.error("Error: ./data/pathway/ already exists.");
-    console.error("Remove it first or use a different directory.");
-    process.exit(1);
-  } catch {
-    // Directory doesn't exist, proceed
-  }
-
-  // Verify starter data is available
-  try {
-    await access(starterDir);
-  } catch {
-    console.error("Error: Starter data not found in package.");
-    console.error("This may indicate a corrupted package installation.");
-    process.exit(1);
-  }
-
-  // Copy starter data
-  console.log("Creating ./data/pathway/ with starter data...\n");
-  await cp(starterDir, dataDir, { recursive: true });
-
-  console.log(`✅ Created ./data/pathway/ with starter data.
-
-Next steps:
-  1. Edit data files to match your organization
-  2. npx fit-map validate
-  3. npx fit-pathway dev
-
-Data structure:
-  data/pathway/
-  ├── framework.yaml        # Framework metadata
-  ├── levels.yaml           # Career levels
-  ├── stages.yaml           # Lifecycle stages
-  ├── drivers.yaml          # Business drivers
-  ├── disciplines/          # Engineering disciplines
-  ├── capabilities/         # Capability areas with skills
-  ├── behaviours/           # Behavioural expectations
-  └── tracks/               # Track specializations
-`);
-}

package/src/lib/job-cache.js

@@ -1,89 +0,0 @@
-/**
- * Job Cache
- *
- * Centralized caching for generated job definitions.
- * Provides consistent key generation and get-or-create pattern.
- */
-
-import { deriveJob } from "@forwardimpact/libskill/derivation";
-
-/** @type {Map<string, Object>} */
-const cache = new Map();
-
-/**
- * Build a consistent cache key from job parameters
- * @param {string} disciplineId
- * @param {string} levelId
- * @param {string} [trackId] - Optional track ID
- * @returns {string}
- */
-export function buildJobKey(disciplineId, levelId, trackId = null) {
-  if (trackId) {
-    return `${disciplineId}_${levelId}_${trackId}`;
-  }
-  return `${disciplineId}_${levelId}`;
-}
-
-/**
- * Get or create a cached job definition
- * @param {Object} params
- * @param {Object} params.discipline
- * @param {Object} params.level
- * @param {Object} [params.track] - Optional track
- * @param {Array} params.skills
- * @param {Array} params.behaviours
- * @param {Array} [params.capabilities]
- * @returns {Object|null}
- */
-export function getOrCreateJob({
-  discipline,
-  level,
-  track = null,
-  skills,
-  behaviours,
-  capabilities,
-}) {
-  const key = buildJobKey(discipline.id, level.id, track?.id);
-
-  if (!cache.has(key)) {
-    const job = deriveJob({
-      discipline,
-      level,
-      track,
-      skills,
-      behaviours,
-      capabilities,
-    });
-    if (job) {
-      cache.set(key, job);
-    }
-    return job;
-  }
-
-  return cache.get(key);
-}
-
-/**
- * Clear all cached jobs
- */
-export function clearCache() {
-  cache.clear();
-}
-
-/**
- * Invalidate a specific job from the cache
- * @param {string} disciplineId
- * @param {string} levelId
- * @param {string} [trackId] - Optional track ID
- */
-export function invalidateCachedJob(disciplineId, levelId, trackId = null) {
-  cache.delete(buildJobKey(disciplineId, levelId, trackId));
-}
-
-/**
- * Get the number of cached jobs (for testing/debugging)
- * @returns {number}
- */
-export function getCachedJobCount() {
-  return cache.size;
-}

package/starter/behaviours/systems_thinking.yaml

@@ -1,32 +0,0 @@
-# yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/behaviour.schema.json
-
-name: Think in Systems
-human:
-  description:
-    The ability to see beyond individual components to understand how the entire
-    system behaves. Engineers recognize that every service, API, and queue is
-    part of a larger whole—isolated changes ripple across the system.
-  maturityDescriptions:
-    emerging:
-      Recognizes that systems have interconnected parts; considers immediate
-      dependencies in code
-    developing:
-      Identifies upstream and downstream impacts; uses observability tools to
-      trace requests across services
-    practicing:
-      Maps complex system interactions across technical and business domains;
-      anticipates cascading effects
-    role_modeling:
-      Shapes systems design practices across their function; influences
-      cross-team architecture decisions
-    exemplifying:
-      Defines organizational systems architecture principles; recognized
-      authority on complex systems
-
-agent:
-  title: Consider the whole system
-  workingStyle: |
-    For every change:
-    1. Identify upstream and downstream impacts
-    2. Consider non-functional requirements (performance, security)
-    3. Document assumptions and trade-offs

package/starter/capabilities/delivery.yaml

@@ -1,105 +0,0 @@
-# yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/capability.schema.json
-
-id: delivery
-name: Delivery
-emojiIcon: "\U0001F680"
-ordinalRank: 1
-description: |
-  Building and shipping solutions that solve real problems.
-professionalResponsibilities:
-  awareness:
-    You complete assigned tasks within established patterns with guidance
-  foundational: You deliver small features end-to-end with minimal guidance
-  working: You own feature delivery from design through deployment
-  practitioner: You lead technical delivery of complex projects across teams
-  expert: You drive delivery of the most critical technical initiatives
-managementResponsibilities:
-  awareness: You track team progress and communicate status to stakeholders
-  foundational:
-    You coordinate team delivery by managing dependencies and removing blockers
-  working: You own team delivery outcomes and make resourcing decisions
-  practitioner: You drive delivery excellence across multiple teams
-  expert: You shape delivery culture across the business unit
-skills:
-  - id: task_completion
-    name: Task Completion
-    human:
-      description:
-        Completing work items reliably, from understanding requirements through
-        implementation to verification.
-      proficiencyDescriptions:
-        awareness:
-          You complete well-defined tasks with guidance, following established
-          patterns and asking for help when needed.
-        foundational:
-          You break down tasks into steps, estimate effort, and deliver
-          independently on familiar work.
-        working:
-          You manage your own workload, handle ambiguous requirements, and
-          consistently deliver on commitments.
-        practitioner:
-          You coordinate task delivery across teams, unblock others, and
-          establish completion standards for your area.
-        expert:
-          You define delivery practices across the organization and drive
-          completion of the most complex initiatives.
-    agent:
-      name: task-completion
-      description: |
-        Guide for completing work items reliably from requirements through
-        verification.
-      useWhen: |
-        Implementing features, fixing bugs, or completing any defined work item.
-      stages:
-        code:
-          focus: |
-            Implement the solution according to requirements. Write clean,
-            tested code that meets acceptance criteria.
-          readChecklist:
-            - Understand the requirements and acceptance criteria
-            - Review relevant existing code and patterns
-          confirmChecklist:
-            - Code compiles and passes tests
-            - Acceptance criteria are met
-            - Changes are documented
-
-  - id: planning
-    name: Planning
-    human:
-      description:
-        Breaking down work into manageable pieces, estimating effort, and
-        sequencing delivery for maximum impact.
-      proficiencyDescriptions:
-        awareness:
-          You follow project plans created by others and report progress
-          accurately.
-        foundational:
-          You create simple plans for your own work, estimate tasks, and
-          identify dependencies.
-        working:
-          You plan features end-to-end, manage dependencies, and adjust plans
-          based on new information.
-        practitioner:
-          You lead planning for complex projects across teams, manage risk, and
-          establish planning practices for your area.
-        expert:
-          You shape planning strategy across the organization and drive delivery
-          of the most complex programmes.
-    agent:
-      name: planning
-      description: |
-        Guide for breaking down work, estimating effort, and sequencing
-        delivery.
-      useWhen: |
-        Planning features, creating implementation plans, or sequencing work.
-      stages:
-        code:
-          focus: |
-            Follow the implementation plan. Track progress and flag deviations
-            from the plan early.
-          readChecklist:
-            - Review the implementation plan
-            - Understand task dependencies and ordering
-          confirmChecklist:
-            - Plan steps are completed in order
-            - Deviations from the plan are documented

package/starter/capabilities/reliability.yaml

@@ -1,72 +0,0 @@
-# yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/capability.schema.json
-
-id: reliability
-name: Reliability
-emojiIcon: "\U0001F6E1\uFE0F"
-ordinalRank: 2
-description: |
-  Ensuring systems are dependable, observable, and resilient.
-professionalResponsibilities:
-  awareness: You follow operational guidelines and escalate issues appropriately
-  foundational:
-    You implement reliability practices in your code and create basic monitoring
-  working: You design for reliability and lead incident response
-  practitioner: You establish SLOs across teams and drive reliability culture
-  expert: You shape reliability strategy across the business unit
-managementResponsibilities:
-  awareness:
-    You understand reliability requirements and support escalation processes
-  foundational:
-    You ensure your team follows reliability practices and facilitate
-    retrospectives
-  working:
-    You own team reliability outcomes and manage incident response rotations
-  practitioner:
-    You drive reliability culture across teams and own cross-team reliability
-    outcomes
-  expert:
-    You shape reliability strategy across the business unit and own enterprise
-    reliability outcomes
-skills:
-  - id: incident_response
-    name: Incident Response
-    human:
-      description:
-        Responding to production incidents effectively, from detection through
-        resolution and post-incident review.
-      proficiencyDescriptions:
-        awareness:
-          You follow incident response procedures and escalate issues using
-          established channels.
-        foundational:
-          You participate in incident response, gather diagnostic information,
-          and contribute to post-incident reviews.
-        working:
-          You lead incident response for your services, coordinate resolution,
-          and conduct blameless post-mortems.
-        practitioner:
-          You establish incident response practices across teams, lead complex
-          incidents, and drive systemic improvements.
-        expert:
-          You define incident management strategy across the organization and
-          lead response to the most critical incidents.
-    agent:
-      name: incident-response
-      description: |
-        Guide for responding to production incidents from detection through
-        resolution.
-      useWhen: |
-        Handling production issues, investigating failures, or improving
-        incident response processes.
-      stages:
-        code:
-          focus: |
-            Implement fixes for identified issues. Ensure changes are tested
-            and do not introduce regressions.
-          readChecklist:
-            - Understand the root cause of the incident
-            - Review affected systems and dependencies
-          confirmChecklist:
-            - Fix addresses the root cause
-            - Changes are tested
-            - Monitoring confirms resolution

package/starter/disciplines/software_engineering.yaml

@@ -1,46 +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
-  - forward_deployed
-  - platform
-
-description:
-  Builds and maintains software systems, focusing on code quality, architecture,
-  and reliable delivery of business value.
-
-# Derivation inputs — one skill per tier
-coreSkills:
-  - task_completion
-supportingSkills:
-  - planning
-broadSkills:
-  - incident_response
-behaviourModifiers:
-  systems_thinking: 1
-
-# Human-specific content
-human:
-  professionalRoleSummary:
-    As a {roleTitle}, you build and maintain software systems that deliver
-    business value reliably.
-  managementRoleSummary:
-    As a {specialization} manager, you lead teams that build and maintain
-    software systems delivering business value.
-
-# Agent-specific content
-agent:
-  identity: |
-    You are a {roleTitle} agent focused on building reliable software.
-  priority: |
-    Write clean, tested code that meets requirements and follows established
-    patterns.
-  constraints:
-    - Follow existing code conventions
-    - Write tests for new functionality
-    - Document non-obvious decisions

package/starter/drivers.yaml

@@ -1,10 +0,0 @@
-# yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/drivers.schema.json
-
-- id: quality
-  name: Quality
-  description: Deliver work that meets expectations consistently.
-  contributingSkills:
-    - task_completion
-    - planning
-  contributingBehaviours:
-    - systems_thinking

package/starter/framework.yaml

@@ -1,49 +0,0 @@
-# yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/framework.schema.json
-
-title: Engineering Pathway
-emojiIcon: "\U0001F9ED"
-description: |
-  Define what good engineering looks like for your organization.
-  Edit these files to match your skills, levels, and expectations.
-
-entityDefinitions:
-  driver:
-    title: Drivers
-    emojiIcon: "\U0001F3AF"
-    description: Organizational outcomes that productive teams achieve.
-  skill:
-    title: Skills
-    emojiIcon: "\U0001F4A1"
-    description: Capabilities required to perform work effectively.
-  behaviour:
-    title: Behaviours
-    emojiIcon: "\U0001F9E0"
-    description: Mindsets and ways of working.
-  discipline:
-    title: Disciplines
-    emojiIcon: "\U0001F52C"
-    description: Engineering specializations that define skill profiles.
-  level:
-    title: Levels
-    emojiIcon: "\U0001F4CA"
-    description: Career levels that define expectations.
-  track:
-    title: Tracks
-    emojiIcon: "\U0001F6E4\uFE0F"
-    description: Work contexts that modify expectations.
-  job:
-    title: Jobs
-    emojiIcon: "\U0001F4CB"
-    description: Role specifications combining discipline, track, and level.
-  agent:
-    title: Agents
-    emojiIcon: "\U0001F916"
-    description: AI agent configurations generated from the framework.
-  stage:
-    title: Stages
-    emojiIcon: "\U0001F504"
-    description: Phases of the engineering lifecycle.
-  tool:
-    title: Tools
-    emojiIcon: "\U0001F527"
-    description: Recommended tools referenced by skills.

package/starter/levels.yaml

@@ -1,39 +0,0 @@
-# yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/levels.schema.json
-
-- id: J040
-  professionalTitle: Level I
-  managementTitle: Associate
-  typicalExperienceRange: "0-2 years"
-  ordinalRank: 1
-  qualificationSummary:
-    Entry-level position suitable for recent graduates or those transitioning
-    into the field ({typicalExperienceRange}).
-  baseSkillProficiencies:
-    primary: foundational
-    secondary: awareness
-    broad: awareness
-  baseBehaviourMaturity: emerging
-  expectations:
-    impactScope: Individual tasks with guidance
-    autonomyExpectation: Work with supervision
-    influenceScope: Contribute to team discussions
-    complexityHandled: Standard tasks with established patterns
-
-- id: J060
-  professionalTitle: Level II
-  managementTitle: Senior Associate
-  typicalExperienceRange: "2-5 years"
-  ordinalRank: 2
-  qualificationSummary:
-    Mid-level position with demonstrated ability to complete tasks independently
-    ({typicalExperienceRange}).
-  baseSkillProficiencies:
-    primary: working
-    secondary: foundational
-    broad: awareness
-  baseBehaviourMaturity: developing
-  expectations:
-    impactScope: Features and small projects
-    autonomyExpectation: Work independently on familiar problems
-    influenceScope: Mentor junior team members
-    complexityHandled: Moderate complexity with some ambiguity

package/starter/stages.yaml

@@ -1,21 +0,0 @@
-# yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/stages.schema.json
-
-- id: code
-  name: Code
-  emojiIcon: "\U0001F4BB"
-  summary: Build the solution
-  description:
-    Your primary task is to implement the solution according to the plan.
-  returnFormat:
-    - "Working code that meets acceptance criteria"
-  handoffs:
-    - targetStage: code
-      label: Continue Coding
-      prompt: Continue implementing the solution.
-  constraints:
-    - Follow the plan and spec requirements
-  readChecklist:
-    - Review the plan and acceptance criteria
-  confirmChecklist:
-    - Code compiles and passes tests
-    - Acceptance criteria are met

package/starter/tracks/forward_deployed.yaml

@@ -1,33 +0,0 @@
-# yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/track.schema.json
-
-name: Forward Deployed
-
-description:
-  Customer-facing engineering embedded with business units. Emphasizes rapid
-  solution delivery and domain expertise. Discovers patterns in the field that
-  Platform Engineers generalize into enterprise capabilities.
-roleContext:
-  In this forward-deployed role, you are embedded directly with business units.
-  You operate like a startup CTO—bridging the gap between building products and
-  solving real business problems through rapid delivery.
-
-skillModifiers:
-  delivery: 1
-  reliability: -1
-behaviourModifiers:
-  systems_thinking: -1
-assessmentWeights:
-  skillWeight: 0.4
-  behaviourWeight: 0.6
-
-agent:
-  identity: |
-    You are a Forward Deployed {roleTitle} agent focused on rapid problem
-    discovery and solution delivery.
-  priority: |
-    Speed matters more than perfection. Deliver working solutions quickly.
-    Discover requirements through immersion, not documentation.
-  constraints:
-    - Deliver working solutions in days, not weeks
-    - Document trade-offs explicitly
-    - Identify candidates for platform generalization

package/starter/tracks/platform.yaml

@@ -1,33 +0,0 @@
-# yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/track.schema.json
-
-name: Platform
-
-description:
-  Internal tooling and infrastructure focus. Builds shared capabilities that
-  enable other engineering teams. Treats the platform as a product with
-  developers as customers.
-roleContext:
-  In this platform-focused role, you build internal tooling and shared
-  infrastructure. You treat the platform as a product—building golden paths and
-  optimizing for developer experience.
-
-skillModifiers:
-  reliability: 1
-  delivery: -1
-behaviourModifiers:
-  systems_thinking: 1
-assessmentWeights:
-  skillWeight: 0.6
-  behaviourWeight: 0.4
-
-agent:
-  identity: |
-    You are a Platform {roleTitle} agent focused on building self-service
-    capabilities that enable other engineers.
-  priority: |
-    Developer experience is paramount. Design golden paths, maintain backward
-    compatibility, and document everything.
-  constraints:
-    - Maintain backward compatibility
-    - Document breaking changes with migration guides
-    - Test changes against consumer use cases