@forwardimpact/pathway 0.3.0 → 0.4.0

package/app/pages/tool.js

@@ -0,0 +1,50 @@
+/**
+ * Tools page
+ *
+ * Displays aggregated tools from all skills with links to skill context.
+ */
+
+import { render, div, h1, p } from "../lib/render.js";
+import { getState } from "../lib/state.js";
+import { prepareToolsList } from "../formatters/tool/shared.js";
+import { createBadge } from "../components/card.js";
+import { createCardList } from "../components/list.js";
+import { toolToCardConfig } from "../lib/card-mappers.js";
+import { getConceptEmoji } from "../model/levels.js";
+
+/**
+ * Render tools list page
+ */
+export function renderToolsList() {
+  const { data } = getState();
+  const { framework } = data;
+  const toolEmoji = getConceptEmoji(framework, "tool");
+
+  const { tools, totalCount } = prepareToolsList(data.skills);
+
+  const page = div(
+    { className: "tools-page" },
+    // Header
+    div(
+      { className: "page-header" },
+      h1(
+        { className: "page-title" },
+        `${toolEmoji} ${framework.entityDefinitions.tool.title}`,
+      ),
+      p(
+        { className: "page-description" },
+        framework.entityDefinitions.tool.description.trim().split("\n")[0],
+      ),
+      createBadge(`${totalCount} tools`, "default"),
+    ),
+
+    // Tools list using standard card grid
+    createCardList(
+      tools,
+      (tool) => toolToCardConfig(tool, data.capabilities),
+      "No tools defined yet.",
+    ),
+  );
+
+  render(page);
+}

package/app/slides/index.js

@@ -55,25 +55,6 @@ export function renderSlideIndex({ render, data }) {
       ),
     ),
 
-    // Tracks
-    div(
-      { className: "slide-section" },
-      a(
-        { href: "#/overview/track" },
-        heading2(
-          { className: "slide-section-title" },
-          `${getConceptEmoji(data.framework, "track")} `,
-          span({ className: "gradient-text" }, "Tracks"),
-        ),
-      ),
-      ul(
-        { className: "related-list" },
-        ...data.tracks.map((track) =>
-          li({}, a({ href: `#/track/${track.id}` }, track.name)),
-        ),
-      ),
-    ),
-
     // Grades
     div(
       { className: "slide-section" },
@@ -99,21 +80,21 @@ export function renderSlideIndex({ render, data }) {
       ),
     ),
 
-    // Skills
+    // Tracks
     div(
       { className: "slide-section" },
       a(
-        { href: "#/overview/skill" },
+        { href: "#/overview/track" },
         heading2(
           { className: "slide-section-title" },
-          `${getConceptEmoji(data.framework, "skill")} `,
-          span({ className: "gradient-text" }, "Skills"),
+          `${getConceptEmoji(data.framework, "track")} `,
+          span({ className: "gradient-text" }, "Tracks"),
         ),
       ),
       ul(
         { className: "related-list" },
-        ...data.skills.map((skill) =>
-          li({}, a({ href: `#/skill/${skill.id}` }, skill.name)),
+        ...data.tracks.map((track) =>
+          li({}, a({ href: `#/track/${track.id}` }, track.name)),
         ),
       ),
     ),
@@ -137,6 +118,25 @@ export function renderSlideIndex({ render, data }) {
       ),
     ),
 
+    // Skills
+    div(
+      { className: "slide-section" },
+      a(
+        { href: "#/overview/skill" },
+        heading2(
+          { className: "slide-section-title" },
+          `${getConceptEmoji(data.framework, "skill")} `,
+          span({ className: "gradient-text" }, "Skills"),
+        ),
+      ),
+      ul(
+        { className: "related-list" },
+        ...data.skills.map((skill) =>
+          li({}, a({ href: `#/skill/${skill.id}` }, skill.name)),
+        ),
+      ),
+    ),
+
     // Drivers
     div(
       { className: "slide-section" },

package/bin/pathway.js

@@ -9,15 +9,17 @@
  *   npx pathway <command> [options]
  *
  * Commands:
- *   skill [<id>]                Show skills (summary, --list, or detail)
- *   behaviour [<id>]            Show behaviours
  *   discipline [<id>]           Show disciplines
  *   grade [<id>]                Show grades
  *   track [<id>]                Show tracks
+ *   behaviour [<id>]            Show behaviours
+ *   skill [<id>]                Show skills (summary, --list, or detail)
  *   driver [<id>]               Show drivers
- *   job [<discipline> <track> <grade>]  Generate job definition
- *   interview <discipline> <track> <grade> [--type=TYPE]  Generate interview
- *   progress <discipline> <track> <grade> [--compare=GRADE]  Career progression
+ *   stage [<id>]                Show stages
+ *   tool [<name>]               Show tools
+ *   job [<discipline> <grade>] [--track=TRACK]  Generate job definition
+ *   interview <discipline> <grade> [--track=TRACK] [--type=TYPE]  Generate interview
+ *   progress <discipline> <grade> [--track=TRACK] [--compare=GRADE]  Career progression
  *   questions [options]         Browse interview questions
  *   agent [<discipline> <track>] [--output=PATH]  Generate AI agent
  *
@@ -37,13 +39,14 @@ import { formatError } from "../app/lib/cli-output.js";
 import { runSchemaValidation } from "../app/model/schema-validation.js";
 
 // Import command handlers
-import { runSkillCommand } from "../app/commands/skill.js";
-import { runBehaviourCommand } from "../app/commands/behaviour.js";
 import { runDisciplineCommand } from "../app/commands/discipline.js";
 import { runGradeCommand } from "../app/commands/grade.js";
 import { runTrackCommand } from "../app/commands/track.js";
+import { runBehaviourCommand } from "../app/commands/behaviour.js";
+import { runSkillCommand } from "../app/commands/skill.js";
 import { runDriverCommand } from "../app/commands/driver.js";
 import { runStageCommand } from "../app/commands/stage.js";
+import { runToolCommand } from "../app/commands/tool.js";
 import { runJobCommand } from "../app/commands/job.js";
 import { runInterviewCommand } from "../app/commands/interview.js";
 import { runProgressCommand } from "../app/commands/progress.js";
@@ -58,13 +61,14 @@ const __dirname = dirname(__filename);
 const rootDir = join(__dirname, "..");
 
 const COMMANDS = {
-  skill: runSkillCommand,
-  behaviour: runBehaviourCommand,
   discipline: runDisciplineCommand,
   grade: runGradeCommand,
   track: runTrackCommand,
+  behaviour: runBehaviourCommand,
+  skill: runSkillCommand,
   driver: runDriverCommand,
   stage: runStageCommand,
+  tool: runToolCommand,
   job: runJobCommand,
   interview: runInterviewCommand,
   progress: runProgressCommand,
@@ -86,19 +90,21 @@ Getting Started:
   site [--output=PATH]                Generate static site to ./site/
 
 Entity Commands (summary by default, --list for IDs, <id> for detail):
-  skill [<id>]                        Browse skills
-  behaviour [<id>]                    Browse behaviours  
   discipline [<id>]                   Browse disciplines
   grade [<id>]                        Browse grades
   track [<id>]                        Browse tracks
+  behaviour [<id>]                    Browse behaviours  
+  skill [<id>]                        Browse skills
+    --agent                           Output as agent SKILL.md format
   driver [<id>]                       Browse drivers
   stage [<id>]                        Browse lifecycle stages
+  tool [<name>]                       Browse recommended tools
 
 Composite Commands:
-  job [<discipline> <track> <grade>]  Generate job definition
-  interview <discipline> <track> <grade> [--type=TYPE]
+  job [<discipline> <grade>] [--track=TRACK]  Generate job definition
+  interview <discipline> <grade> [--track=TRACK] [--type=TYPE]
                                       Generate interview questions
-  progress <discipline> <track> <grade> [--compare=GRADE]
+  progress <discipline> <grade> [--track=TRACK] [--compare=GRADE]
                                       Show career progression
   questions [filters]                 Browse interview questions
   agent <discipline> [--track=<track>] Generate AI coding agent
@@ -130,11 +136,17 @@ Examples:
   npx pathway skill                    # Summary of all skills
   npx pathway skill --list             # Skill IDs for piping
   npx pathway skill ai_evaluation      # Detail view
+  npx pathway skill architecture_design --agent  # Agent SKILL.md output
+
+  npx pathway tool                     # Summary of all tools
+  npx pathway tool --list              # Tool names for piping
+  npx pathway tool DuckDB              # Tool detail with skill usages
 
   npx pathway job                      # Summary of valid combinations
   npx pathway job --list               # All combinations for piping
-  npx pathway job software_engineering platform L4
-  npx pathway job se platform L3 --checklist=code_to_review
+  npx pathway job software_engineering L4
+  npx pathway job software_engineering L4 --track=platform
+  npx pathway job se L3 --track=platform --checklist=code
 
   npx pathway questions --level=practitioner
   npx pathway questions --stats
@@ -176,6 +188,7 @@ function parseArgs(args) {
     output: null,
     stage: null,
     "all-stages": false,
+    agent: false,
     // Serve command options
     port: null,
     // Init command options
@@ -227,6 +240,8 @@ function parseArgs(args) {
       result.stage = arg.slice(8);
     } else if (arg === "--all-stages") {
       result["all-stages"] = true;
+    } else if (arg === "--agent") {
+      result.agent = true;
     } else if (arg.startsWith("--checklist=")) {
       result.checklist = arg.slice(12);
     } else if (arg.startsWith("--port=")) {

package/examples/capabilities/business.yaml

@@ -102,10 +102,10 @@ skills:
           initiatives.
     agent:
       name: technical-writing
-      description: |
-        Guide for creating clear technical documentation. Use when writing
-        READMEs, API docs, specifications, or any technical content that needs
-        to be clear and accurate.
+      description: Guide for creating clear technical documentation.
+      useWhen: |
+        Writing READMEs, API docs, specifications, or any technical content
+        that needs to be clear and accurate.
       stages:
         specify:
           focus: |
@@ -172,18 +172,18 @@ skills:
             - Audience can discover and find it
             - Search and navigation are updated
             - Maintenance schedule is established
-      reference: |
-        ## Document Types
+    implementationReference: |
+      ## Document Types
 
-        | Type | Purpose | Key Sections |
-        |------|---------|--------------|
-        | README | Project overview | Description, Getting Started, Usage |
-        | API Docs | API reference | Endpoints, Parameters, Examples |
-        | Spec | Design proposal | Problem, Solution, Alternatives |
-        | Tutorial | Learning guide | Objective, Steps, Outcomes |
+      | Type | Purpose | Key Sections |
+      |------|---------|--------------|
+      | README | Project overview | Description, Getting Started, Usage |
+      | API Docs | API reference | Endpoints, Parameters, Examples |
+      | Spec | Design proposal | Problem, Solution, Alternatives |
+      | Tutorial | Learning guide | Objective, Steps, Outcomes |
 
-        ## Writing Principles
-        - Use simple, direct language
-        - One idea per sentence
-        - Active voice over passive
-        - Lead with most important info
+      ## Writing Principles
+      - Use simple, direct language
+      - One idea per sentence
+      - Active voice over passive
+      - Lead with most important info

package/examples/capabilities/delivery.yaml

@@ -73,10 +73,11 @@ skills:
           architecture authority.
     agent:
       name: architecture-design
-      description: |
+      description:
         Guide for designing software systems and making architectural decisions.
-        Use when asked to design a system, evaluate architecture options, or
-        make structural decisions about code organization.
+      useWhen: |
+        Asked to design a system, evaluate architecture options, or make
+        structural decisions about code organization.
       stages:
         specify:
           focus: |
@@ -144,23 +145,23 @@ skills:
             - Performance meets requirements
             - Monitoring confirms design assumptions
             - Operational procedures are documented
-      reference: |
-        ## Common Patterns
+    implementationReference: |
+      ## Common Patterns
 
-        ### Service Architecture
-        - **Microservices**: Independent deployment, clear boundaries
-        - **Monolith**: Simpler deployment, easier refactoring
-        - **Modular monolith**: Boundaries within single deployment
+      ### Service Architecture
+      - **Microservices**: Independent deployment, clear boundaries
+      - **Monolith**: Simpler deployment, easier refactoring
+      - **Modular monolith**: Boundaries within single deployment
 
-        ### Data Patterns
-        - **Event sourcing**: Full audit trail, complex queries
-        - **CQRS**: Separate read and write models
-        - **Repository pattern**: Abstract data access
+      ### Data Patterns
+      - **Event sourcing**: Full audit trail, complex queries
+      - **CQRS**: Separate read and write models
+      - **Repository pattern**: Abstract data access
 
-        ### Communication Patterns
-        - **REST**: Synchronous, request-response
-        - **Event-driven**: Asynchronous, loose coupling
-        - **gRPC**: Efficient, strongly typed
+      ### Communication Patterns
+      - **REST**: Synchronous, request-response
+      - **Event-driven**: Asynchronous, loose coupling
+      - **gRPC**: Efficient, strongly typed
   - id: full_stack_development
     name: Full-Stack Development
     human:
@@ -195,10 +196,11 @@ skills:
           polymathic engineering.
     agent:
       name: full-stack-development
-      description: |
+      description:
         Guide for building complete solutions across the full technology stack.
-        Use when implementing features spanning frontend, backend, database,
-        and infrastructure layers.
+      useWhen: |
+        Implementing features spanning frontend, backend, database, and
+        infrastructure layers.
       stages:
         specify:
           focus: |
@@ -266,23 +268,36 @@ skills:
             - Feature works end-to-end in production
             - No errors in monitoring
             - Performance meets requirements
-      reference: |
-        ## Technology Stack
+    toolReferences:
+      - name: Terraform
+        url: https://developer.hashicorp.com/terraform/docs
+        description: Infrastructure as code tool
+        useWhen: Provisioning and managing cloud infrastructure
+      - name: CloudFormation
+        url: https://docs.aws.amazon.com/cloudformation/
+        description: AWS infrastructure as code service
+        useWhen: Managing AWS infrastructure as code
+      - name: Docker
+        url: https://docs.docker.com/
+        description: Container platform
+        useWhen: Containerizing applications or managing container environments
+    implementationReference: |
+      ## Technology Stack
 
-        ### Primary Languages
-        - **JavaScript/TypeScript**: Frontend and Node.js backend
-        - **Python**: Backend APIs and data processing
+      ### Primary Languages
+      - **JavaScript/TypeScript**: Frontend and Node.js backend
+      - **Python**: Backend APIs and data processing
 
-        ### Infrastructure
-        - **Terraform**: Cloud infrastructure as code
-        - **CloudFormation**: AWS-specific infrastructure
-        - **Docker**: Containerization
+      ### Infrastructure
+      - **Terraform**: Cloud infrastructure as code
+      - **CloudFormation**: AWS-specific infrastructure
+      - **Docker**: Containerization
 
-        ## Layer Responsibilities
+      ## Layer Responsibilities
 
-        | Layer | Responsibilities |
-        |-------|-----------------|
-        | Frontend | UI/UX, client validation, API integration |
-        | Backend | Business logic, auth, external services |
-        | Database | Persistence, queries, migrations |
-        | Infrastructure | Deployment, scaling, monitoring |
+      | Layer | Responsibilities |
+      |-------|-----------------|
+      | Frontend | UI/UX, client validation, API integration |
+      | Backend | Business logic, auth, external services |
+      | Database | Persistence, queries, migrations |
+      | Infrastructure | Deployment, scaling, monitoring |