@forwardimpact/pathway 0.25.22 → 0.25.25

package/src/lib/cli-output.js

@@ -1,129 +1,12 @@
 /**
- * CLI Output Formatting Utilities
+ * Domain-specific CLI Output Formatters
  *
- * Provides consistent formatting for terminal output including colors,
- * tables, headers, and level formatting.
+ * Pathway-specific formatting for skill proficiencies, behaviour maturities,
+ * modifiers, percentages, and change indicators. Generic formatters (colors,
+ * tables, headers, etc.) live in @forwardimpact/libcli.
  */
 
-// ANSI color codes
-export const colors = {
-  reset: "\x1b[0m",
-  bold: "\x1b[1m",
-  dim: "\x1b[2m",
-  italic: "\x1b[3m",
-  underline: "\x1b[4m",
-  red: "\x1b[31m",
-  green: "\x1b[32m",
-  yellow: "\x1b[33m",
-  blue: "\x1b[34m",
-  magenta: "\x1b[35m",
-  cyan: "\x1b[36m",
-  white: "\x1b[37m",
-  gray: "\x1b[90m",
-};
-
-/**
- * Check if stdout supports colors
- * @returns {boolean}
- */
-export function supportsColor() {
-  if (process.env.NO_COLOR) return false;
-  if (process.env.FORCE_COLOR) return true;
-  return process.stdout.isTTY;
-}
-
-/**
- * Wrap text with color if supported
- * @param {string} text
- * @param {string} color
- * @returns {string}
- */
-function colorize(text, color) {
-  if (!supportsColor()) return text;
-  return `${color}${text}${colors.reset}`;
-}
-
-/**
- * Format a header
- * @param {string} text
- * @returns {string}
- */
-export function formatHeader(text) {
-  return colorize(text, colors.bold + colors.cyan);
-}
-
-/**
- * Format a subheader
- * @param {string} text
- * @returns {string}
- */
-export function formatSubheader(text) {
-  return colorize(text, colors.bold);
-}
-
-/**
- * Format a list item
- * @param {string} label
- * @param {string} value
- * @param {number} [indent=0]
- * @returns {string}
- */
-export function formatListItem(label, value, indent = 0) {
-  const padding = "  ".repeat(indent);
-  const bullet = colorize("•", colors.dim);
-  return `${padding}${bullet} ${label}: ${value}`;
-}
-
-/**
- * Format a bullet item (no label)
- * @param {string} text
- * @param {number} [indent=0]
- * @returns {string}
- */
-export function formatBullet(text, indent = 0) {
-  const padding = "  ".repeat(indent);
-  const bullet = colorize("•", colors.dim);
-  return `${padding}${bullet} ${text}`;
-}
-
-/**
- * Format a table
- * @param {string[]} headers
- * @param {Array<Array<string|number>>} rows
- * @param {Object} [options]
- * @param {boolean} [options.compact=false]
- * @returns {string}
- */
-export function formatTable(headers, rows, options = {}) {
-  const { compact = false } = options;
-
-  // Calculate column widths
-  const widths = headers.map((h, i) =>
-    Math.max(String(h).length, ...rows.map((r) => String(r[i] || "").length)),
-  );
-
-  const lines = [];
-
-  // Header
-  const headerLine = headers
-    .map((h, i) => String(h).padEnd(widths[i]))
-    .join("  ");
-  lines.push(colorize(headerLine, colors.bold));
-
-  // Separator
-  if (!compact) {
-    lines.push(widths.map((w) => "─".repeat(w)).join("──"));
-  }
-
-  // Rows
-  for (const row of rows) {
-    lines.push(
-      row.map((cell, i) => String(cell || "").padEnd(widths[i])).join("  "),
-    );
-  }
-
-  return lines.join("\n");
-}
+import { colorize, colors } from "@forwardimpact/libcli";
 
 /**
  * Format skill proficiency with color
@@ -193,78 +76,15 @@ export function formatPercent(value) {
 }
 
 /**
- * Format a change indicator (↑, ↓, →)
+ * Format a change indicator
  * @param {number} change
  * @returns {string}
  */
 export function formatChange(change) {
   if (change > 0) {
-    return colorize(`↑${change}`, colors.green);
+    return colorize(`\u2191${change}`, colors.green);
   } else if (change < 0) {
-    return colorize(`↓${Math.abs(change)}`, colors.red);
+    return colorize(`\u2193${Math.abs(change)}`, colors.red);
   }
-  return colorize("→", colors.dim);
-}
-
-/**
- * Format an error message
- * @param {string} message
- * @returns {string}
- */
-export function formatError(message) {
-  return colorize(`Error: ${message}`, colors.red);
-}
-
-/**
- * Format a success message
- * @param {string} message
- * @returns {string}
- */
-export function formatSuccess(message) {
-  return colorize(message, colors.green);
-}
-
-/**
- * Format a warning message
- * @param {string} message
-/**
- * Format a warning message
- * @param {string} message
- * @returns {string}
- */
-export function formatWarning(message) {
-  return colorize(`Warning: ${message}`, colors.yellow);
-}
-
-/**
- * Create a horizontal rule
- * @param {number} [width=60]
- * @returns {string}
- */
-export function horizontalRule(width = 60) {
-  return colorize("─".repeat(width), colors.dim);
-}
-
-/**
- * Format a section with title and content
- * @param {string} title
- * @param {string} content
- * @returns {string}
- */
-export function formatSection(title, content) {
-  return `${formatHeader(title)}\n\n${content}`;
-}
-
-/**
- * Indent all lines of text
- * @param {string} text
- * @param {number} [spaces=2]
- * @returns {string}
- */
-export function indent(text, spaces = 2) {
-  const padding = " ".repeat(spaces);
-  return text
-    .split("\n")
-    .map((line) => padding + line)
-    .join("\n");
+  return colorize("\u2192", colors.dim);
 }

package/src/pages/agent-builder-install.js

@@ -56,13 +56,14 @@ export function getApmInstallCommand(siteUrl, packName) {
 }
 
 /**
- * Build the `npx skills add` command that discovers the published pack
- * registry at `<siteUrl>/.well-known/agent-skills/index.json`.
+ * Build the `npx skills add` command that discovers the per-pack skill
+ * repository at `<siteUrl>/packs/<packName>/.well-known/skills/index.json`.
  * @param {string} siteUrl
+ * @param {string} packName
  * @returns {string}
  */
-export function getSkillsAddCommand(siteUrl) {
-  return `npx skills add ${normalizeSiteUrl(siteUrl)}`;
+export function getSkillsAddCommand(siteUrl, packName) {
+  return `npx skills add ${normalizeSiteUrl(siteUrl)}/packs/${packName}`;
 }
 
 /**
@@ -80,7 +81,7 @@ export function createInstallSection({ discipline, track, siteUrl }) {
 
   const packName = getPackName(discipline, track);
   const apmCommand = getApmInstallCommand(siteUrl, packName);
-  const skillsCommand = getSkillsAddCommand(siteUrl);
+  const skillsCommand = getSkillsAddCommand(siteUrl, packName);
 
   return section(
     {

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/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