@forwardimpact/map 0.11.0

package/examples/behaviours/relentless_curiosity.yaml

@@ -0,0 +1,37 @@
+# yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/behaviour.schema.json
+
+name: Don't Lose Your Curiosity
+human:
+  description:
+    The driving force behind learning and invention. Protect your instinct to
+    break things down and understand them deeply. Embrace an experimental spirit
+    that treats failure as a path to discovery, not a setback to avoid.
+  maturityDescriptions:
+    emerging:
+      Asks basic questions when prompted; shows interest in learning about
+      immediate tasks; willing to try new approaches
+    developing:
+      Regularly asks clarifying questions about "why" and "how"; explores
+      related topics with guidance; experiments without fear of failure;
+      investigates how AI tools work rather than using them blindly
+    practicing:
+      Proactively investigates root causes; experiments with new technologies
+      and AI capabilities; protects time for exploration; treats failure as
+      learning; discovers requirements through immersion in problem spaces
+    role_modeling:
+      Drives team curiosity through challenging questions; creates environments
+      where exploration and experimentation are encouraged; models problem
+      discovery orientation; seeks out ambiguity rather than avoiding it
+    exemplifying:
+      Shapes organizational culture around curiosity and continuous learning;
+      sponsors experimental initiatives across the organization; recognized
+      externally as a thought leader in problem discovery; influences industry
+      practices around innovation and exploration
+
+agent:
+  title: Investigate before acting
+  workingStyle: |
+    Before taking action:
+    1. Confirm your understanding of the goal
+    2. Identify unknowns that could affect the approach
+    3. Research unfamiliar areas via subagent if needed

package/examples/behaviours/systems_thinking.yaml

@@ -0,0 +1,40 @@
+# 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. Like understanding how reintroducing wolves to Yellowstone
+    transformed not just deer but rivers, 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; understands basic cause-and-effect
+    developing:
+      Identifies upstream and downstream impacts; uses observability tools to
+      trace requests across services; understands feedback loops; maps
+      dependencies before making changes
+    practicing:
+      Maps complex system interactions across technical and business domains;
+      anticipates cascading effects; designs systems that degrade gracefully;
+      understands how technology changes impact business operations
+    role_modeling:
+      Shapes systems design practices across their function; conducts chaos
+      engineering experiments; influences cross-team architecture decisions;
+      creates clarity from complexity; bridges technical systems with business
+      processes
+    exemplifying:
+      Defines organizational systems architecture principles; recognized
+      industry authority on complex systems; advises executive leadership on
+      systemic risks and opportunities; publishes thought leadership on systems
+      thinking in technology organizations
+
+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/examples/capabilities/_index.yaml

@@ -0,0 +1,8 @@
+# Auto-generated index for browser loading
+# Do not edit manually - regenerate with: npx pathway --generate-index
+files:
+  - business
+  - delivery
+  - people
+  - reliability
+  - scale

package/examples/capabilities/business.yaml

@@ -0,0 +1,205 @@
+# yaml-language-server: $schema=https://www.forwardimpact.team/schema/json/capability.schema.json
+
+name: Business
+emojiIcon: 💼
+ordinalRank: 8
+description: |
+  Understanding and driving business value.
+  Includes domain knowledge, stakeholder management, strategic thinking,
+  and translating between technical and business contexts.
+professionalResponsibilities:
+  awareness:
+    You understand the business context for your assigned work and communicate
+    progress clearly when asked
+  foundational:
+    You connect your technical work to business outcomes, engage with
+    stakeholders to clarify requirements
+  working:
+    You translate business needs into technical solutions, manage stakeholder
+    expectations, and articulate technical decisions in business terms
+  practitioner:
+    You drive business outcomes through technical solutions across your area,
+    influence product roadmaps, and partner effectively with business
+    stakeholders
+  expert:
+    You shape technology-driven business strategy, represent the technical
+    perspective at executive level, and are recognized as a bridge between
+    engineering and business
+managementResponsibilities:
+  awareness:
+    You understand business context and communicate team progress to
+    stakeholders with guidance
+  foundational:
+    You align team priorities with business objectives, manage stakeholder
+    relationships, and communicate team impact
+  working:
+    You translate business strategy into team objectives, own stakeholder
+    relationships, and ensure your team delivers business value
+  practitioner:
+    You partner with business leaders to shape strategy for your area, influence
+    direction across teams, and deliver measurable business impact
+  expert:
+    You shape technology-driven business strategy, represent engineering at
+    executive level, and own strategic business outcomes
+skills:
+  - id: stakeholder_management
+    name: Stakeholder Management
+    isHumanOnly: true
+    human:
+      description:
+        Building relationships with and managing expectations of stakeholders
+        across the organization, from frontline workers to C-level executives
+      proficiencyDescriptions:
+        awareness:
+          You identify key stakeholders for your work and communicate status
+          when asked. You understand that different stakeholders have different
+          needs.
+        foundational:
+          You proactively update stakeholders on progress, handle basic
+          expectation setting, and escalate concerns appropriately. You build
+          rapport with regular collaborators.
+        working:
+          You manage multiple stakeholders with different interests, navigate
+          conflicting priorities diplomatically, and build trust through
+          consistent delivery. You tailor communication to each audience.
+        practitioner:
+          You influence senior stakeholders effectively across your area, manage
+          complex stakeholder landscapes with competing agendas, build trust
+          rapidly with new stakeholders, and shield teams from organizational
+          friction.
+        expert:
+          You shape stakeholder practices across the business unit. You manage
+          executive relationships, represent engineering at the highest levels,
+          and are recognized for exceptional stakeholder partnerships.
+  - id: technical_writing
+    name: Technical Writing
+    human:
+      description:
+        Creating clear, accurate, and useful technical documentation. Good specs
+        enable AI to generate accurate solutions; poor specs lead to poor
+        results.
+      proficiencyDescriptions:
+        awareness:
+          You document your own work following team templates and standards. You
+          keep code comments current and write basic README content.
+        foundational:
+          You write clear READMEs, inline documentation, and technical guides.
+          You update existing docs when making changes and ensure documentation
+          matches implementation.
+        working:
+          You create comprehensive documentation for complex systems. You write
+          precise specifications that enable accurate AI-generated code,
+          establish documentation practices for your projects, and ensure docs
+          are discoverable.
+        practitioner:
+          You define documentation standards across teams in your area, create
+          documentation systems and templates, train engineers on spec-driven
+          development, and ensure documentation quality across projects.
+        expert:
+          You shape documentation culture and standards across the business
+          unit. You innovate on documentation approaches, are recognized for
+          exceptional technical writing clarity, and lead documentation
+          initiatives.
+    agent:
+      name: technical-writing
+      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: |
+            Define documentation requirements and audience needs.
+            Clarify what the documentation must accomplish.
+          readChecklist:
+            - Identify target audience and their skill level
+            - Document what questions the docs must answer
+            - Define documentation type (README, API, spec, tutorial)
+            - Specify accuracy and completeness requirements
+            - Mark ambiguities with [NEEDS CLARIFICATION]
+          confirmChecklist:
+            - Audience is identified
+            - Questions to answer are documented
+            - Documentation type is chosen
+            - Requirements are clear
+        plan:
+          focus: Understanding audience and planning documentation
+          readChecklist:
+            - Identify target audience and their needs
+            - Determine document type and structure
+            - List prerequisites and assumptions
+            - Outline key sections and content
+          confirmChecklist:
+            - Audience is identified
+            - Document type and structure planned
+            - Prerequisites listed
+            - Outline complete
+        onboard:
+          focus: |
+            Set up the documentation environment. Install documentation
+            tools, configure rendering, and verify preview works.
+          readChecklist:
+            - Install documentation framework (MkDocs, Docusaurus, etc.)
+            - Configure markdown linter (markdownlint)
+            - Set up diagram rendering (Mermaid, PlantUML)
+            - Configure spell checker (cspell)
+            - Verify documentation preview server works
+          confirmChecklist:
+            - Documentation framework builds without errors
+            - Markdown linter runs and catches issues
+            - Diagrams render correctly in preview
+            - Spell checker configured with project dictionary
+            - Preview server shows formatted documentation
+        code:
+          focus: Writing clear and accurate documentation
+          readChecklist:
+            - Write using simple, direct language
+            - Structure content for scanning
+            - Include tested, runnable examples
+            - Define technical terms
+          confirmChecklist:
+            - Purpose clear in first paragraph
+            - Examples are tested and work
+            - Technical terms are defined
+            - Structure supports scanning
+        review:
+          focus: Verifying documentation quality
+          readChecklist:
+            - Check accuracy against implementation
+            - Verify examples are runnable
+            - Review for clarity and completeness
+            - Test with target audience if possible
+          confirmChecklist:
+            - Documentation matches implementation
+            - All examples verified working
+            - No ambiguous pronouns
+            - Structure is logical and complete
+        deploy:
+          focus: |
+            Publish documentation and ensure it reaches the audience.
+            Set up maintenance process.
+          readChecklist:
+            - Publish to documentation site
+            - Announce to relevant teams
+            - Add to search indexes and navigation
+            - Establish update and review schedule
+          confirmChecklist:
+            - Documentation is published and accessible
+            - Audience can discover and find it
+            - Search and navigation are updated
+            - Maintenance schedule is established
+    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 |
+
+      ## Writing Principles
+      - Use simple, direct language
+      - One idea per sentence
+      - Active voice over passive
+      - Lead with most important info