@forwardimpact/pathway 0.25.7 → 0.25.9

package/src/commands/level.js

@@ -4,10 +4,10 @@
  * Handles level summary, listing, and detail display in the terminal.
  *
  * Usage:
- *   npx pathway level              # Summary with stats
- *   npx pathway level --list       # IDs only (for piping)
- *   npx pathway level <id>         # Detail view
- *   npx pathway level --validate   # Validation checks
+ *   bunx pathway level              # Summary with stats
+ *   bunx pathway level --list       # IDs only (for piping)
+ *   bunx pathway level <id>         # Detail view
+ *   bunx pathway level --validate   # Validation checks
  */
 
 import { createEntityCommand } from "./command-factory.js";
@@ -57,8 +57,8 @@ function formatSummary(levels, data) {
     ),
   );
   console.log(`\nTotal: ${levels.length} levels`);
-  console.log(`\nRun 'npx pathway level --list' for IDs and titles`);
-  console.log(`Run 'npx pathway level <id>' for details\n`);
+  console.log(`\nRun 'bunx pathway level --list' for IDs and titles`);
+  console.log(`Run 'bunx pathway level <id>' for details\n`);
 }
 
 /**

package/src/commands/progress.js

@@ -4,9 +4,9 @@
  * Shows career progression analysis in the terminal.
  *
  * Usage:
- *   npx pathway progress <discipline> <level>                            # Progress for trackless job
- *   npx pathway progress <discipline> <level> --track=<track>            # Progress with track
- *   npx pathway progress <discipline> <from_level> --compare=<to_level>  # Compare levels
+ *   bunx pathway progress <discipline> <level>                            # Progress for trackless job
+ *   bunx pathway progress <discipline> <level> --track=<track>            # Progress with track
+ *   bunx pathway progress <discipline> <from_level> --compare=<to_level>  # Compare levels
  */
 
 import { createCompositeCommand } from "./command-factory.js";
@@ -80,5 +80,5 @@ export const runProgressCommand = createCompositeCommand({
     }),
   formatter: formatProgress,
   usageExample:
-    "npx pathway progress software_engineering L3 --track=platform --compare=L4",
+    "bunx pathway progress software_engineering L3 --track=platform --compare=L4",
 });

package/src/commands/questions.js

@@ -4,10 +4,10 @@
  * Browse and compare interview questions across skills and behaviours.
  *
  * Usage:
- *   npx pathway questions                    # Summary with stats
- *   npx pathway questions --list             # Question IDs (for piping)
- *   npx pathway questions --level=practitioner  # Filter by level
- *   npx pathway questions --stats            # Detailed statistics
+ *   bunx pathway questions                    # Summary with stats
+ *   bunx pathway questions --list             # Question IDs (for piping)
+ *   bunx pathway questions --level=practitioner  # Filter by level
+ *   bunx pathway questions --stats            # Detailed statistics
  */
 
 import {
@@ -97,9 +97,9 @@ function showQuestionsSummary(data) {
   console.log("\nBehaviour Questions:");
   console.log(formatTable(["Maturity", "Count"], behaviourRows));
 
-  console.log(`\nRun 'npx pathway questions --list' for question IDs`);
-  console.log(`Run 'npx pathway questions --stats' for detailed stats`);
-  console.log(`Run 'npx pathway questions --level=practitioner' to filter\n`);
+  console.log(`\nRun 'bunx pathway questions --list' for question IDs`);
+  console.log(`Run 'bunx pathway questions --stats' for detailed stats`);
+  console.log(`Run 'bunx pathway questions --level=practitioner' to filter\n`);
 }
 
 /**

package/src/commands/skill.js

@@ -4,11 +4,11 @@
  * Handles skill summary, listing, and detail display in the terminal.
  *
  * Usage:
- *   npx pathway skill              # Summary with stats
- *   npx pathway skill --list       # IDs only (for piping)
- *   npx pathway skill <id>         # Detail view
- *   npx pathway skill <id> --agent # Agent SKILL.md output
- *   npx pathway skill --validate   # Validation checks
+ *   bunx pathway skill              # Summary with stats
+ *   bunx pathway skill --list       # IDs only (for piping)
+ *   bunx pathway skill <id>         # Detail view
+ *   bunx pathway skill <id> --agent # Agent SKILL.md output
+ *   bunx pathway skill --validate   # Validation checks
  */
 
 import { createEntityCommand } from "./command-factory.js";
@@ -40,8 +40,8 @@ function formatSummary(skills, data) {
 
   console.log(formatTable(["Capability", "Count", "Agent"], rows));
   console.log(`\nTotal: ${skills.length} skills`);
-  console.log(`\nRun 'npx pathway skill --list' for IDs`);
-  console.log(`Run 'npx pathway skill <id>' for details\n`);
+  console.log(`\nRun 'bunx pathway skill --list' for IDs`);
+  console.log(`Run 'bunx pathway skill <id>' for details\n`);
 }
 
 /**
@@ -73,7 +73,7 @@ async function formatAgentDetail(skill, stages, templateLoader, dataDir) {
     console.error(formatError(`Skill '${skill.id}' has no agent section`));
     console.error(`\nSkills with agent support:`);
     console.error(
-      `  npx pathway skill --list | xargs -I{} sh -c 'npx pathway skill {} --json | jq -e .skill.agent > /dev/null && echo {}'`,
+      `  bunx pathway skill --list | xargs -I{} sh -c 'bunx pathway skill {} --json | jq -e .skill.agent > /dev/null && echo {}'`,
     );
     process.exit(1);
   }

package/src/commands/stage.js

@@ -4,9 +4,9 @@
  * Handles stage summary, listing, and detail display in the terminal.
  *
  * Usage:
- *   npx pathway stage              # Summary with lifecycle flow
- *   npx pathway stage --list       # IDs only (for piping)
- *   npx pathway stage <id>         # Detail view
+ *   bunx pathway stage              # Summary with lifecycle flow
+ *   bunx pathway stage --list       # IDs only (for piping)
+ *   bunx pathway stage <id>         # Detail view
  */
 
 import { createEntityCommand } from "./command-factory.js";
@@ -52,8 +52,8 @@ function formatSummary(stages, _data) {
 
   console.log(formatTable(["ID", "Name", "Mode", "Tools", "Handoffs"], rows));
   console.log(`\nTotal: ${stages.length} stages`);
-  console.log(`\nRun 'npx pathway stage --list' for IDs and names`);
-  console.log(`Run 'npx pathway stage <id>' for details\n`);
+  console.log(`\nRun 'bunx pathway stage --list' for IDs and names`);
+  console.log(`Run 'bunx pathway stage <id>' for details\n`);
 }
 
 /**

package/src/commands/tool.js

@@ -4,9 +4,9 @@
  * Handles tool summary, listing, and detail display in the terminal.
  *
  * Usage:
- *   npx pathway tool              # Summary with stats
- *   npx pathway tool --list       # Tool names only (for piping)
- *   npx pathway tool <name>       # Detail view for specific tool
+ *   bunx pathway tool              # Summary with stats
+ *   bunx pathway tool --list       # Tool names only (for piping)
+ *   bunx pathway tool <name>       # Detail view for specific tool
  */
 
 import { truncate } from "../formatters/shared.js";
@@ -89,9 +89,9 @@ function formatSummary(tools, totalCount) {
     console.log(`(showing top 15 by usage)`);
   }
   console.log(
-    `\nRun 'npx pathway tool --list' for all tool names and descriptions`,
+    `\nRun 'bunx pathway tool --list' for all tool names and descriptions`,
   );
-  console.log(`Run 'npx pathway tool <name>' for details\n`);
+  console.log(`Run 'bunx pathway tool <name>' for details\n`);
 }
 
 /**

package/src/commands/track.js

@@ -4,10 +4,10 @@
  * Handles track summary, listing, and detail display in the terminal.
  *
  * Usage:
- *   npx pathway track              # Summary with stats
- *   npx pathway track --list       # IDs only (for piping)
- *   npx pathway track <id>         # Detail view
- *   npx pathway track --validate   # Validation checks
+ *   bunx pathway track              # Summary with stats
+ *   bunx pathway track --list       # IDs only (for piping)
+ *   bunx pathway track <id>         # Detail view
+ *   bunx pathway track --validate   # Validation checks
  */
 
 import { createEntityCommand } from "./command-factory.js";
@@ -49,8 +49,8 @@ function formatSummary(tracks, data) {
 
   console.log(formatTable(["ID", "Name", "Modifiers", "Disciplines"], rows));
   console.log(`\nTotal: ${tracks.length} tracks`);
-  console.log(`\nRun 'npx pathway track --list' for IDs and names`);
-  console.log(`Run 'npx pathway track <id>' for details\n`);
+  console.log(`\nRun 'bunx pathway track --list' for IDs and names`);
+  console.log(`Run 'bunx pathway track <id>' for details\n`);
 }
 
 /**

package/src/formatters/agent/dom.js

@@ -18,6 +18,7 @@ import { getStageEmoji } from "../stage/shared.js";
  * @param {Array} deployment.skills - Agent skills
  * @param {Array} [deployment.roleAgents] - Role variant agents (plan, review)
  * @param {Object} [deployment.claudeCodeSettings] - Claude Code settings to include in download
+ * @param {string|null} [deployment.teamInstructions] - Team instructions content for CLAUDE.md
  * @returns {HTMLElement}
  */
 export function agentDeploymentToDOM({
@@ -25,6 +26,7 @@ export function agentDeploymentToDOM({
   skills,
   roleAgents = [],
   claudeCodeSettings = {},
+  teamInstructions = null,
 }) {
   const profileContent = formatAgentProfile(profile);
   const agentName = profile.frontmatter.name;
@@ -39,6 +41,7 @@ export function agentDeploymentToDOM({
       roleAgents,
       claudeCodeSettings,
       agentName,
+      teamInstructions,
     ),
 
     // Profile section
@@ -92,6 +95,7 @@ export function agentDeploymentToDOM({
  * @param {Array} roleAgents - Role variant agents
  * @param {Object} claudeCodeSettings - Claude Code settings to include
  * @param {string} agentName - Agent name for zip filename
+ * @param {string|null} teamInstructions - Team instructions content for CLAUDE.md
  * @returns {HTMLElement}
  */
 function createDownloadButton(
@@ -100,6 +104,7 @@ function createDownloadButton(
   roleAgents,
   claudeCodeSettings,
   agentName,
+  teamInstructions,
 ) {
   const btn = button(
     { className: "btn btn-primary download-all-btn" },
@@ -117,6 +122,7 @@ function createDownloadButton(
         roleAgents,
         claudeCodeSettings,
         agentName,
+        teamInstructions,
       );
     } finally {
       btn.disabled = false;
@@ -169,6 +175,7 @@ function createRoleAgentCard(agent) {
  * @param {Array} roleAgents - Role variant agents
  * @param {Object} claudeCodeSettings - Claude Code settings to include
  * @param {string} agentName - Agent name for zip filename
+ * @param {string|null} teamInstructions - Team instructions content for CLAUDE.md
  */
 async function downloadAllAsZip(
   profile,
@@ -176,6 +183,7 @@ async function downloadAllAsZip(
   roleAgents,
   claudeCodeSettings,
   agentName,
+  teamInstructions,
 ) {
   // Dynamically import JSZip
   const JSZip = await importJSZip();
@@ -185,6 +193,11 @@ async function downloadAllAsZip(
   const profileContent = formatAgentProfile(profile);
   zip.file(`.claude/agents/${profile.filename}`, profileContent);
 
+  // Add team instructions to .claude/CLAUDE.md
+  if (teamInstructions) {
+    zip.file(".claude/CLAUDE.md", teamInstructions.trim() + "\n");
+  }
+
   // Add role agent profiles to .claude/agents/ folder
   for (const roleAgent of roleAgents) {
     const roleContent = formatAgentProfile(roleAgent);

package/src/formatters/questions/yaml.js

@@ -26,7 +26,7 @@ export function questionsToYaml(view, _options = {}) {
 
   const filterStr =
     filterParts.length > 0 ? filterParts.join(" ") : "(no filters)";
-  const header = `# Generated by: npx pathway questions ${filterStr}\n# Questions: ${questions.length}\n\n`;
+  const header = `# Generated by: bunx pathway questions ${filterStr}\n# Questions: ${questions.length}\n\n`;
 
   // Group questions by source
   const bySource = {};

package/src/index.html

@@ -83,7 +83,7 @@
         <div class="top-bar__command">
           <span class="top-bar__prompt">$</span>
           <span class="top-bar__command-text" id="cli-command"
-            >npx fit-pathway</span
+            >bunx fit-pathway</span
           >
           <button class="top-bar__copy" id="cli-copy" aria-label="Copy command">
             <svg viewBox="0 0 24 24">

package/src/lib/cli-command.js

@@ -1,7 +1,7 @@
 /**
  * CLI Command Mapping
  *
- * Maps hash routes to their equivalent `npx fit-pathway` CLI commands.
+ * Maps hash routes to their equivalent `bunx fit-pathway` CLI commands.
  */
 
 /**
@@ -11,122 +11,122 @@
  */
 const ROUTE_COMMANDS = [
   // Landing
-  { pattern: /^\/$/, toCommand: () => "npx fit-pathway" },
+  { pattern: /^\/$/, toCommand: () => "bunx fit-pathway" },
 
   // Entity lists
-  { pattern: /^\/skill$/, toCommand: () => "npx fit-pathway skill" },
-  { pattern: /^\/behaviour$/, toCommand: () => "npx fit-pathway behaviour" },
+  { pattern: /^\/skill$/, toCommand: () => "bunx fit-pathway skill" },
+  { pattern: /^\/behaviour$/, toCommand: () => "bunx fit-pathway behaviour" },
   {
     pattern: /^\/discipline$/,
-    toCommand: () => "npx fit-pathway discipline",
+    toCommand: () => "bunx fit-pathway discipline",
   },
-  { pattern: /^\/track$/, toCommand: () => "npx fit-pathway track" },
-  { pattern: /^\/level$/, toCommand: () => "npx fit-pathway level" },
-  { pattern: /^\/driver$/, toCommand: () => "npx fit-pathway driver" },
-  { pattern: /^\/stage$/, toCommand: () => "npx fit-pathway stage" },
-  { pattern: /^\/tool$/, toCommand: () => "npx fit-pathway tool" },
+  { pattern: /^\/track$/, toCommand: () => "bunx fit-pathway track" },
+  { pattern: /^\/level$/, toCommand: () => "bunx fit-pathway level" },
+  { pattern: /^\/driver$/, toCommand: () => "bunx fit-pathway driver" },
+  { pattern: /^\/stage$/, toCommand: () => "bunx fit-pathway stage" },
+  { pattern: /^\/tool$/, toCommand: () => "bunx fit-pathway tool" },
 
   // Entity details
   {
     pattern: /^\/skill\/(.+)$/,
-    toCommand: (m) => `npx fit-pathway skill ${m[1]}`,
+    toCommand: (m) => `bunx fit-pathway skill ${m[1]}`,
   },
   {
     pattern: /^\/behaviour\/(.+)$/,
-    toCommand: (m) => `npx fit-pathway behaviour ${m[1]}`,
+    toCommand: (m) => `bunx fit-pathway behaviour ${m[1]}`,
   },
   {
     pattern: /^\/discipline\/(.+)$/,
-    toCommand: (m) => `npx fit-pathway discipline ${m[1]}`,
+    toCommand: (m) => `bunx fit-pathway discipline ${m[1]}`,
   },
   {
     pattern: /^\/track\/(.+)$/,
-    toCommand: (m) => `npx fit-pathway track ${m[1]}`,
+    toCommand: (m) => `bunx fit-pathway track ${m[1]}`,
   },
   {
     pattern: /^\/level\/(.+)$/,
-    toCommand: (m) => `npx fit-pathway level ${m[1]}`,
+    toCommand: (m) => `bunx fit-pathway level ${m[1]}`,
   },
   {
     pattern: /^\/driver\/(.+)$/,
-    toCommand: (m) => `npx fit-pathway driver ${m[1]}`,
+    toCommand: (m) => `bunx fit-pathway driver ${m[1]}`,
   },
   {
     pattern: /^\/stage\/(.+)$/,
-    toCommand: (m) => `npx fit-pathway stage ${m[1]}`,
+    toCommand: (m) => `bunx fit-pathway stage ${m[1]}`,
   },
 
   // Job builder + detail
   {
     pattern: /^\/job-builder$/,
-    toCommand: () => "npx fit-pathway job --list",
+    toCommand: () => "bunx fit-pathway job --list",
   },
   {
     pattern: /^\/job\/([^/]+)\/([^/]+)\/([^/]+)$/,
-    toCommand: (m) => `npx fit-pathway job ${m[1]} ${m[2]} --track=${m[3]}`,
+    toCommand: (m) => `bunx fit-pathway job ${m[1]} ${m[2]} --track=${m[3]}`,
   },
   {
     pattern: /^\/job\/([^/]+)\/([^/]+)$/,
-    toCommand: (m) => `npx fit-pathway job ${m[1]} ${m[2]}`,
+    toCommand: (m) => `bunx fit-pathway job ${m[1]} ${m[2]}`,
   },
 
   // Interview builder + detail
   {
     pattern: /^\/interview-prep$/,
-    toCommand: () => "npx fit-pathway interview --list",
+    toCommand: () => "bunx fit-pathway interview --list",
   },
   {
     pattern: /^\/interview\/([^/]+)\/([^/]+)\/([^/]+)$/,
     toCommand: (m) =>
-      `npx fit-pathway interview ${m[1]} ${m[2]} --track=${m[3]}`,
+      `bunx fit-pathway interview ${m[1]} ${m[2]} --track=${m[3]}`,
   },
   {
     pattern: /^\/interview\/([^/]+)\/([^/]+)$/,
-    toCommand: (m) => `npx fit-pathway interview ${m[1]} ${m[2]}`,
+    toCommand: (m) => `bunx fit-pathway interview ${m[1]} ${m[2]}`,
   },
 
   // Career progress builder + detail
   {
     pattern: /^\/career-progress$/,
-    toCommand: () => "npx fit-pathway progress --list",
+    toCommand: () => "bunx fit-pathway progress --list",
   },
   {
     pattern: /^\/progress\/([^/]+)\/([^/]+)\/([^/]+)$/,
     toCommand: (m) =>
-      `npx fit-pathway progress ${m[1]} ${m[2]} --track=${m[3]}`,
+      `bunx fit-pathway progress ${m[1]} ${m[2]} --track=${m[3]}`,
   },
   {
     pattern: /^\/progress\/([^/]+)\/([^/]+)$/,
-    toCommand: (m) => `npx fit-pathway progress ${m[1]} ${m[2]}`,
+    toCommand: (m) => `bunx fit-pathway progress ${m[1]} ${m[2]}`,
   },
 
   // Self-assessment
   {
     pattern: /^\/self-assessment$/,
-    toCommand: () => "npx fit-pathway self-assessment",
+    toCommand: () => "bunx fit-pathway self-assessment",
   },
   {
     pattern: /^\/self-assessment\/results$/,
-    toCommand: () => "npx fit-pathway self-assessment",
+    toCommand: () => "bunx fit-pathway self-assessment",
   },
 
   // Agent builder + detail
   {
     pattern: /^\/agent-builder$/,
-    toCommand: () => "npx fit-pathway agent --list",
+    toCommand: () => "bunx fit-pathway agent --list",
   },
   {
     pattern: /^\/agent\/([^/]+)\/([^/]+)\/([^/]+)$/,
     toCommand: (m) =>
-      `npx fit-pathway agent ${m[1]} --track=${m[2]} --stage=${m[3]}`,
+      `bunx fit-pathway agent ${m[1]} --track=${m[2]} --stage=${m[3]}`,
   },
   {
     pattern: /^\/agent\/([^/]+)\/([^/]+)$/,
-    toCommand: (m) => `npx fit-pathway agent ${m[1]} --track=${m[2]}`,
+    toCommand: (m) => `bunx fit-pathway agent ${m[1]} --track=${m[2]}`,
   },
   {
     pattern: /^\/agent\/([^/]+)$/,
-    toCommand: (m) => `npx fit-pathway agent ${m[1]}`,
+    toCommand: (m) => `bunx fit-pathway agent ${m[1]}`,
   },
 ];
 
@@ -141,5 +141,5 @@ export function getCliCommand(hashPath) {
     const match = path.match(pattern);
     if (match) return toCommand(match);
   }
-  return "npx fit-pathway";
+  return "bunx fit-pathway";
 }

package/starter/behaviours/systems_thinking.yaml

@@ -0,0 +1,32 @@
+# 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

@@ -0,0 +1,105 @@
+# 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

@@ -0,0 +1,72 @@
+# 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