@forwardimpact/pathway 0.1.0

package/examples/drivers.yaml

@@ -0,0 +1,205 @@
+# Drivers - What outcomes matter?
+# Organizational outcomes that productive teams achieve
+# Links skills and behaviours to business impact
+
+# Direction & Strategy
+- id: clear_direction
+  name: Clear Direction
+  description:
+    The degree to which developers understand their team's mission, goals, and
+    alignment with the greater organization
+  contributingSkills:
+    - stakeholder_management
+    - technical_writing
+  contributingBehaviours:
+    - polymathic_knowledge
+    - systems_thinking
+
+- id: say_on_priorities
+  name: Say on Priorities
+  description:
+    The involvement and influence developers hold in shaping their team's
+    direction and tasks
+  contributingSkills:
+    - stakeholder_management
+    - team_collaboration
+  contributingBehaviours:
+    - outcome_ownership
+    - relentless_curiosity
+
+- id: requirements_quality
+  name: Requirements Quality
+  description:
+    How well specifications are defined for tasks and projects, encompassing
+    completeness and stability of requirements
+  contributingSkills:
+    - stakeholder_management
+    - technical_writing
+    - architecture_design
+  contributingBehaviours:
+    - precise_communication
+    - systems_thinking
+
+# Delivery & Release
+- id: ease_of_release
+  name: Ease of Release
+  description:
+    The amount of friction involved in releasing code to end-users, encompassing
+    validation, packaging, and deployment
+  contributingSkills:
+    - devops
+    - code_quality
+    - full_stack_development
+    - cloud_platforms
+  contributingBehaviours:
+    - outcome_ownership
+    - precise_communication
+
+- id: test_efficiency
+  name: Test Efficiency
+  description:
+    The speed and stability of an automated test suite, affecting feedback loops
+    in the software development lifecycle
+  contributingSkills:
+    - full_stack_development
+    - code_quality
+    - devops
+  contributingBehaviours:
+    - outcome_ownership
+    - relentless_curiosity
+
+- id: managing_tech_debt
+  name: Managing Tech Debt
+  description:
+    Continuously identifying, analyzing, and addressing technical debt to
+    maintain developer productivity
+  contributingSkills:
+    - code_quality
+    - architecture_design
+  contributingBehaviours:
+    - outcome_ownership
+    - systems_thinking
+
+# Quality & Documentation
+- id: code_review
+  name: Code Review
+  description:
+    The timeliness and quality of feedback received during code review, as well
+    as the experience of reviewing others' code
+  contributingSkills:
+    - code_quality
+    - team_collaboration
+  contributingBehaviours:
+    - precise_communication
+    - relentless_curiosity
+
+- id: documentation
+  name: Documentation
+  description:
+    Helping developers obtain the information they need to understand and
+    complete technical tasks
+  contributingSkills:
+    - technical_writing
+  contributingBehaviours:
+    - precise_communication
+    - polymathic_knowledge
+
+- id: codebase_experience
+  name: Codebase Experience
+  description:
+    The ease of understanding and modifying code, significantly affecting
+    overall developer experience
+  contributingSkills:
+    - code_quality
+    - architecture_design
+  contributingBehaviours:
+    - relentless_curiosity
+    - polymathic_knowledge
+
+# Operations & Reliability
+- id: incident_response
+  name: Incident Response
+  description:
+    How developers handle and resolve issues in their systems, including triage,
+    resolution, and communication
+  contributingSkills:
+    - sre_practices
+    - devops
+    - cloud_platforms
+  contributingBehaviours:
+    - outcome_ownership
+    - systems_thinking
+
+# Learning & Growth
+- id: learning_culture
+  name: Learning Culture
+  description:
+    The team characteristic of continuously improving and learning from past
+    experience
+  contributingSkills:
+    - team_collaboration
+    - technical_writing
+  contributingBehaviours:
+    - relentless_curiosity
+    - polymathic_knowledge
+
+- id: experimentation
+  name: Experimentation
+  description:
+    Activities that generate new ideas, test hypotheses, and capture insights
+    from experiments
+  contributingSkills:
+    - data_modeling
+    - full_stack_development
+  contributingBehaviours:
+    - relentless_curiosity
+    - polymathic_knowledge
+
+# Team & Collaboration
+- id: connectedness
+  name: Connectedness
+  description:
+    The state of feeling linked and related to others at work, fostered through
+    communication and interaction
+  contributingSkills:
+    - team_collaboration
+    - stakeholder_management
+  contributingBehaviours:
+    - precise_communication
+    - polymathic_knowledge
+
+- id: efficient_processes
+  name: Efficient Processes
+  description:
+    How effectively team members collaborate to design and deliver software
+    using principles and workflows
+  contributingSkills:
+    - team_collaboration
+    - devops
+  contributingBehaviours:
+    - precise_communication
+    - outcome_ownership
+
+- id: deep_work
+  name: Deep Work
+  description:
+    The ability to focus on tasks without distraction, achieved by minimizing
+    interruptions and context switching
+  contributingSkills:
+    - architecture_design
+    - code_quality
+  contributingBehaviours:
+    - relentless_curiosity
+    - precise_communication
+
+# User Focus
+- id: leveraging_user_feedback
+  name: Leveraging User Feedback
+  description:
+    Collecting, analyzing, and taking action based on insights from end-users
+  contributingSkills:
+    - stakeholder_management
+    - data_modeling
+  contributingBehaviours:
+    - relentless_curiosity
+    - precise_communication

package/examples/framework.yaml

@@ -0,0 +1,58 @@
+# Framework - High-level definitions about the Engineering Pathway
+# Drives page content for landing page, entity list pages, and handout chapters
+
+title: Engineering Pathway
+emoji: "🧭"
+tag: "#AcmeCorp"
+description: |
+  A unified framework for human and AI collaboration in engineering. Define roles, track skills and behaviours, build career paths, and generate AI coding agents—all from the same coherent foundation. The pathway aligns human capabilities with AI assistance, enabling productive teams in the AI era.
+
+# Entity definitions for pages and chapters
+entityDefinitions:
+  driver:
+    title: Drivers
+    emoji: "🎯"
+    description: |
+      Organizational outcomes that productive teams achieve. Drivers link skills and behaviours to business value, helping teams understand how their capabilities contribute to organizational success.
+
+  skill:
+    title: Skills
+    emoji: "💡"
+    description: |
+      Capabilities required to perform work effectively. Skills are organized by capability and measured across five levels from Awareness to Expert. They form the foundation of technical and professional competence.
+
+  behaviour:
+    title: Behaviours
+    emoji: "🧠"
+    description: |
+      Mindsets and ways of working that underpin effective application of skills. Behaviours are measured across five maturity levels from Emerging to Exemplifying. They describe how engineers approach their work, collaborate with others, and drive outcomes.
+
+  discipline:
+    title: Disciplines
+    emoji: "🔧"
+    description: |
+      Engineering specializations that define T-shaped skill profiles. Each discipline specifies primary skills for deep expertise, secondary skills for supporting capabilities, and broad skills for general awareness. Disciplines answer the question: "What kind of engineer are you?"
+
+  grade:
+    title: Grades
+    emoji: "📊"
+    description: |
+      Career levels that define expectations for skill proficiency, behaviour maturity, and scope of impact. Grades provide a clear progression path from entry-level to distinguished leadership roles, with defined expectations at each stage.
+
+  track:
+    title: Tracks
+    emoji: "🛤️"
+    description: |
+      Work contexts that modify skill and behaviour expectations based on the nature of the role. Tracks answer the question: "Where and how do you work?" They apply modifiers to adjust expectations for different working environments and responsibilities.
+
+  job:
+    title: Jobs
+    emoji: "📋"
+    description: |
+      Complete role specifications that combine discipline, track, and grade into actionable job definitions with skill matrices, behaviour profiles, and derived responsibilities. Jobs represent the practical application of the framework to define concrete engineering positions.
+
+  agent:
+    title: Agents
+    emoji: "🤖"
+    description: |
+      AI coding agent configurations generated from the same disciplines, tracks, and skills that define human roles. Agent profiles and skills follow the GitHub Copilot specification, ensuring AI assistants understand context, constraints, and working styles aligned with human engineering expectations.

package/examples/grades.yaml

@@ -0,0 +1,118 @@
+# Grades - What career level?
+# Base skill levels and behaviour maturities by seniority
+# See domain-concepts.instructions.md for level progressions
+
+- id: L1
+  professionalTitle: Engineer I
+  managementTitle: Associate Manager
+  typicalExperienceRange: "0-2"
+  ordinalRank: 1
+  qualificationSummary:
+    Entry-level position for those new to the field or transitioning careers.
+    Bachelor's degree or equivalent practical experience.
+  baseSkillLevels:
+    primary: foundational
+    secondary: awareness
+    broad: awareness
+  baseBehaviourMaturity: emerging
+  expectations:
+    impactScope:
+      Individual tasks and small features with guidance from senior team members
+    autonomyExpectation:
+      Work with close supervision and ask for help when encountering challenges
+    influenceScope:
+      Contribute to team discussions and learn from experienced colleagues
+    complexityHandled:
+      Standard tasks with established patterns and clear requirements
+
+- id: L2
+  professionalTitle: Engineer II
+  managementTitle: Manager
+  typicalExperienceRange: "2-5"
+  ordinalRank: 2
+  qualificationSummary:
+    2-5 years of relevant experience. Demonstrated ability to complete tasks
+    independently and contribute effectively to team projects.
+  baseSkillLevels:
+    primary: foundational
+    secondary: foundational
+    broad: awareness
+  baseBehaviourMaturity: emerging
+  expectations:
+    impactScope: Complete features and components delivered independently
+    autonomyExpectation:
+      Work independently on familiar problems while seeking guidance on novel
+      situations
+    influenceScope:
+      Help onboard new team members and participate actively in code reviews
+    complexityHandled: Moderate complexity with some ambiguity in requirements
+
+- id: L3
+  professionalTitle: Senior Engineer
+  managementTitle: Senior Manager
+  typicalExperienceRange: "5-8"
+  ordinalRank: 3
+  qualificationSummary:
+    5-8 years of relevant experience. Proven track record of leading technical
+    initiatives and mentoring team members.
+  baseSkillLevels:
+    primary: practitioner
+    secondary: working
+    broad: foundational
+  baseBehaviourMaturity: developing
+  expectations:
+    impactScope:
+      Large features and technical initiatives including leading small projects
+    autonomyExpectation:
+      Do self-directed work while seeking input on strategic decisions
+    influenceScope: Shape team practices and mentor junior engineers
+    complexityHandled: High complexity with comfort navigating ambiguity
+
+- id: L4
+  professionalTitle: Staff Engineer
+  managementTitle: Director
+  typicalExperienceRange: "8-12"
+  ordinalRank: 4
+  qualificationSummary:
+    8-12 years of relevant experience. Extensive experience leading complex
+    technical projects with multi-team impact.
+  baseSkillLevels:
+    primary: expert
+    secondary: practitioner
+    broad: working
+  baseBehaviourMaturity: practicing
+  breadthCriteria:
+    practitioner: 4
+  expectations:
+    impactScope: Multi-team initiatives with organizational impact
+    autonomyExpectation: Set own direction within broader strategic goals
+    influenceScope:
+      Influence multiple teams and be recognized as a domain expert
+    complexityHandled:
+      Very high complexity driving through ambiguity to deliver results
+
+- id: L5
+  professionalTitle: Principal Engineer
+  managementTitle: VP of Engineering
+  typicalExperienceRange: "12+"
+  ordinalRank: 5
+  qualificationSummary:
+    12+ years of relevant experience. Deep technical expertise with a proven
+    track record of organization-wide technical leadership.
+  baseSkillLevels:
+    primary: expert
+    secondary: expert
+    broad: practitioner
+  baseBehaviourMaturity: role_modeling
+  breadthCriteria:
+    practitioner: 5
+    expert: 2
+  expectations:
+    impactScope:
+      Organization-wide technical strategy and architectural direction
+    autonomyExpectation:
+      Define strategic direction and be accountable for outcomes
+    influenceScope:
+      Shape organizational practices and maintain external industry visibility
+    complexityHandled:
+      Organizational-scale complexity creating clarity from chaos

package/examples/questions/behaviours/outcome_ownership.yaml

@@ -0,0 +1,52 @@
+# outcome_ownership questions
+# See skills.yaml or behaviours.yaml for metadata
+
+emerging:
+  - id: own_emerg_1
+    text: Describe a task you completed from start to finish.
+    lookingFor:
+      - Follow-through
+      - Basic accountability
+    expectedDurationMinutes: 5
+developing:
+  - id: own_dev_1
+    text: Tell me about a time when you took responsibility for a mistake.
+    lookingFor:
+      - Accountability
+      - Learning from errors
+    expectedDurationMinutes: 5
+practicing:
+  - id: own_pract_1
+    text:
+      Describe a project where you owned the entire lifecycle from design to
+      production support.
+    lookingFor:
+      - End-to-end ownership
+      - Operational responsibility
+    expectedDurationMinutes: 8
+role_modeling:
+  - id: own_role_1
+    text: How do you build a culture of ownership in your team?
+    lookingFor:
+      - Team accountability
+      - Systemic approaches
+    expectedDurationMinutes: 8
+exemplifying:
+  - id: own_exemp_1
+    text:
+      How do you establish and drive ownership culture across an entire
+      organization?
+    followUps:
+      - How do you balance ownership with collaboration?
+    lookingFor:
+      - Enterprise ownership culture
+      - Accountability at scale
+    expectedDurationMinutes: 10
+  - id: own_exemp_2
+    text:
+      How do you hold yourself and others accountable for outcomes at an
+      organizational level?
+    lookingFor:
+      - Executive-level accountability
+      - Systemic ownership practices
+    expectedDurationMinutes: 10

package/examples/questions/behaviours/polymathic_knowledge.yaml

@@ -0,0 +1,48 @@
+# polymathic_knowledge questions
+# See skills.yaml or behaviours.yaml for metadata
+
+emerging:
+  - id: poly_emerg_1
+    text: What interests do you have outside your primary technical domain?
+    lookingFor:
+      - Breadth of interests
+      - Cross-disciplinary awareness
+    expectedDurationMinutes: 5
+developing:
+  - id: poly_dev_1
+    text: Describe a time when knowledge from one area helped you in another.
+    lookingFor:
+      - Cross-domain application
+      - Creative problem solving
+    expectedDurationMinutes: 5
+practicing:
+  - id: poly_pract_1
+    text: How do you approach problems that span multiple disciplines?
+    lookingFor:
+      - Integration of knowledge
+      - Holistic thinking
+    expectedDurationMinutes: 8
+role_modeling:
+  - id: poly_role_1
+    text: How do you encourage cross-disciplinary learning in your organization?
+    lookingFor:
+      - Creating learning opportunities
+      - Breaking down silos
+    expectedDurationMinutes: 8
+exemplifying:
+  - id: poly_exemp_1
+    text: How do you build and promote polymathic culture across an enterprise?
+    followUps:
+      - How do you break down organizational silos?
+    lookingFor:
+      - Enterprise cross-disciplinary leadership
+      - Silo breaking at scale
+    expectedDurationMinutes: 10
+  - id: poly_exemp_2
+    text:
+      How do you personally maintain breadth across multiple domains while
+      achieving depth? How do you model this for others?
+    lookingFor:
+      - Personal polymathic practice
+      - Modeling breadth and depth balance
+    expectedDurationMinutes: 10

package/examples/questions/behaviours/precise_communication.yaml

@@ -0,0 +1,55 @@
+# precise_communication questions
+# See skills.yaml or behaviours.yaml for metadata
+
+emerging:
+  - id: comm_emerg_1
+    text:
+      Tell me about a time when you had to explain something technical to
+      someone less familiar with the topic.
+    lookingFor:
+      - Ability to simplify concepts
+      - Awareness of audience
+    expectedDurationMinutes: 5
+developing:
+  - id: comm_dev_1
+    text: Describe how you approach writing documentation for your work.
+    lookingFor:
+      - Clear writing habits
+      - Consideration of readers
+    expectedDurationMinutes: 5
+practicing:
+  - id: comm_pract_1
+    text:
+      Tell me about presenting a complex technical topic to diverse
+      stakeholders.
+    lookingFor:
+      - Audience adaptation
+      - Facilitation skills
+    expectedDurationMinutes: 8
+role_modeling:
+  - id: comm_role_1
+    text: How have you improved communication practices in your organization?
+    lookingFor:
+      - Leadership in communication
+      - Systemic improvements
+    expectedDurationMinutes: 8
+exemplifying:
+  - id: comm_exemp_1
+    text:
+      How do you shape communication culture across an enterprise and represent
+      your organization externally?
+    followUps:
+      - How do you coach executives on technical communication?
+    lookingFor:
+      - Enterprise communication leadership
+      - External representation
+      - Communication excellence at all levels
+    expectedDurationMinutes: 10
+  - id: comm_exemp_2
+    text:
+      Describe how you've established communication standards that span
+      technical and business audiences across the organization.
+    lookingFor:
+      - Cross-functional communication leadership
+      - Scalable communication practices
+    expectedDurationMinutes: 10

package/examples/questions/behaviours/relentless_curiosity.yaml

@@ -0,0 +1,51 @@
+# relentless_curiosity questions
+# See skills.yaml or behaviours.yaml for metadata
+
+emerging:
+  - id: cur_emerg_1
+    text: What new technology or concept have you learned recently?
+    lookingFor:
+      - Evidence of learning
+      - Interest beyond immediate work
+    expectedDurationMinutes: 5
+developing:
+  - id: cur_dev_1
+    text:
+      Tell me about a time when you went beyond the requirements to understand
+      something deeper.
+    lookingFor:
+      - Self-directed exploration
+      - Root cause thinking
+    expectedDurationMinutes: 5
+practicing:
+  - id: cur_pract_1
+    text: How do you stay current with developments in your field?
+    lookingFor:
+      - Systematic learning approach
+      - Breadth of interests
+    expectedDurationMinutes: 5
+role_modeling:
+  - id: cur_role_1
+    text: How do you foster a culture of curiosity in your team?
+    lookingFor:
+      - Creating learning environments
+      - Encouraging exploration
+    expectedDurationMinutes: 8
+exemplifying:
+  - id: cur_exemp_1
+    text:
+      How do you shape organizational culture around curiosity and continuous
+      learning at an enterprise level?
+    followUps:
+      - How do you sponsor experimental initiatives?
+    lookingFor:
+      - Enterprise learning culture leadership
+      - Sponsoring innovation and experimentation
+    expectedDurationMinutes: 10
+  - id: cur_exemp_2
+    text:
+      How do you influence industry practices around innovation and exploration?
+    lookingFor:
+      - External thought leadership
+      - Industry-level influence on learning culture
+    expectedDurationMinutes: 10

package/examples/questions/behaviours/systems_thinking.yaml

@@ -0,0 +1,53 @@
+# systems_thinking questions
+# See skills.yaml or behaviours.yaml for metadata
+
+emerging:
+  - id: sys_emerg_1
+    text:
+      How do you consider the impact of your code changes on other parts of the
+      system?
+    lookingFor:
+      - Awareness of dependencies
+      - Basic impact thinking
+    expectedDurationMinutes: 5
+developing:
+  - id: sys_dev_1
+    text:
+      Describe a time when you identified an unintended consequence of a change.
+    lookingFor:
+      - Systemic awareness
+      - Proactive identification
+    expectedDurationMinutes: 5
+practicing:
+  - id: sys_pract_1
+    text: How do you approach understanding a complex system you're new to?
+    lookingFor:
+      - Systematic exploration
+      - Mapping approaches
+    expectedDurationMinutes: 8
+role_modeling:
+  - id: sys_role_1
+    text: How do you help others develop systems thinking capabilities?
+    lookingFor:
+      - Teaching approaches
+      - Creating visibility
+    expectedDurationMinutes: 8
+exemplifying:
+  - id: sys_exemp_1
+    text:
+      How do you define enterprise-wide systems architecture principles and
+      influence organizational thinking?
+    followUps:
+      - How do you advise executive leadership on complex systems?
+    lookingFor:
+      - Enterprise systems thinking leadership
+      - Executive advisory on complexity
+    expectedDurationMinutes: 10
+  - id: sys_exemp_2
+    text:
+      How do you bridge technical systems with business processes at an
+      organizational scale?
+    lookingFor:
+      - Business-technical systems integration
+      - Enterprise complexity management
+    expectedDurationMinutes: 10

package/examples/questions/skills/architecture_design.yaml

@@ -0,0 +1,54 @@
+# architecture_design questions
+# See skills.yaml or behaviours.yaml for metadata
+
+awareness:
+  - id: arch_aware_1
+    text: What do you understand by 'separation of concerns' in software design?
+    lookingFor:
+      - Basic understanding of modularity
+      - Recognition that different parts of a system should handle different
+        things
+    expectedDurationMinutes: 5
+foundational:
+  - id: arch_found_1
+    text:
+      Walk me through a recent feature you built. How did you decide on the
+      structure?
+    followUps:
+      - What alternatives did you consider?
+      - What would you do differently?
+    lookingFor:
+      - Evidence of thoughtful design decisions
+      - Understanding of common patterns
+    expectedDurationMinutes: 8
+working:
+  - id: arch_work_1
+    text:
+      Describe a system you designed. What were the key trade-offs you had to
+      make?
+    followUps:
+      - How did you validate these decisions?
+    lookingFor:
+      - Clear articulation of trade-offs
+      - Evidence of independent design work
+    expectedDurationMinutes: 8
+practitioner:
+  - id: arch_pract_1
+    text:
+      Tell me about a time when you had to guide a team through a significant
+      architectural decision.
+    followUps:
+      - How did you handle disagreements?
+    lookingFor:
+      - Leadership in technical decisions
+      - Ability to build consensus
+    expectedDurationMinutes: 8
+expert:
+  - id: arch_expert_1
+    text:
+      How do you approach defining and evolving architectural standards for an
+      organization?
+    lookingFor:
+      - Strategic thinking about architecture
+      - Experience with organizational influence
+    expectedDurationMinutes: 8