@forwardimpact/schema 0.1.0

package/examples/questions/skills/cloud_platforms.yaml

@@ -0,0 +1,47 @@
+# yaml-language-server: $schema=https://schema.forwardimpact.team/json/skill-questions.schema.json
+
+awareness:
+  - id: cp_aware_1
+    text: What cloud platforms are you familiar with?
+    lookingFor:
+      - Basic cloud awareness
+      - Understanding of cloud services
+    expectedDurationMinutes: 5
+
+foundational:
+  - id: cp_found_1
+    text: How would you deploy a simple application to the cloud?
+    lookingFor:
+      - Basic deployment knowledge
+      - Understanding of cloud resources
+    expectedDurationMinutes: 8
+
+working:
+  - id: cp_work_1
+    text:
+      Describe a cloud architecture you've designed. What services did you use
+      and why?
+    followUps:
+      - How did you handle cost optimization?
+    lookingFor:
+      - Practical cloud architecture experience
+      - Service selection rationale
+    expectedDurationMinutes: 10
+
+practitioner:
+  - id: cp_pract_1
+    text:
+      How do you approach cloud cost optimization and governance for your team?
+    lookingFor:
+      - Cloud cost management
+      - Governance practices
+    expectedDurationMinutes: 8
+
+expert:
+  - id: cp_expert_1
+    text:
+      How have you shaped cloud strategy and practices across an organization?
+    lookingFor:
+      - Enterprise cloud strategy
+      - Multi-cloud or hybrid considerations
+    expectedDurationMinutes: 10

package/examples/questions/skills/code_quality.yaml

@@ -0,0 +1,48 @@
+# yaml-language-server: $schema=https://schema.forwardimpact.team/json/skill-questions.schema.json
+
+awareness:
+  - id: cq_aware_1
+    text: What does 'clean code' mean to you?
+    lookingFor:
+      - Basic understanding of readability
+      - Awareness of maintainability concerns
+    expectedDurationMinutes: 5
+
+foundational:
+  - id: cq_found_1
+    text: How do you ensure the code you write is readable by others?
+    followUps:
+      - What naming conventions do you follow?
+      - How do you decide when to add comments?
+    lookingFor:
+      - Consistent coding practices
+      - Understanding of code formatting and structure
+    expectedDurationMinutes: 5
+
+working:
+  - id: cq_work_1
+    text: How do you approach code review? What do you look for?
+    lookingFor:
+      - Systematic approach to reviews
+      - Balance between quality and velocity
+    expectedDurationMinutes: 8
+
+practitioner:
+  - id: cq_pract_1
+    text: How have you improved code quality practices in your team?
+    lookingFor:
+      - Measurable improvements
+      - Team influence
+    expectedDurationMinutes: 8
+
+expert:
+  - id: cq_expert_1
+    text:
+      How have you established code quality standards across an organization?
+    followUps:
+      - How did you gain adoption?
+      - How do you measure success?
+    lookingFor:
+      - Organizational influence
+      - Scalable quality practices
+    expectedDurationMinutes: 10

package/examples/questions/skills/data_modeling.yaml

@@ -0,0 +1,45 @@
+# yaml-language-server: $schema=https://schema.forwardimpact.team/json/skill-questions.schema.json
+
+awareness:
+  - id: dm_aware_1
+    text: What's the difference between relational and non-relational databases?
+    lookingFor:
+      - Basic database concepts
+      - Understanding of use cases for each
+    expectedDurationMinutes: 5
+foundational:
+  - id: dm_found_1
+    text:
+      How would you design a simple database schema for a user management
+      system?
+    lookingFor:
+      - Basic schema design
+      - Understanding of normalization
+    expectedDurationMinutes: 8
+working:
+  - id: dm_work_1
+    text: Describe a data model you've designed. What trade-offs did you make?
+    followUps:
+      - How did you handle performance?
+    lookingFor:
+      - Practical data modeling experience
+      - Performance considerations
+    expectedDurationMinutes: 10
+practitioner:
+  - id: dm_pract_1
+    text:
+      How do you approach data modeling for complex domains with evolving
+      requirements?
+    lookingFor:
+      - Advanced modeling techniques
+      - Handling schema evolution
+    expectedDurationMinutes: 10
+expert:
+  - id: dm_expert_1
+    text:
+      How do you establish data modeling standards and practices across an
+      organization?
+    lookingFor:
+      - Enterprise data architecture
+      - Organizational standards leadership
+    expectedDurationMinutes: 10

package/examples/questions/skills/devops.yaml

@@ -0,0 +1,46 @@
+# yaml-language-server: $schema=https://schema.forwardimpact.team/json/skill-questions.schema.json
+
+awareness:
+  - id: devops_aware_1
+    text: What do you understand about CI/CD pipelines? How have you used them?
+    lookingFor:
+      - Basic understanding of automated builds and deployments
+      - Experience using pipelines defined by others
+    expectedDurationMinutes: 5
+foundational:
+  - id: devops_found_1
+    text: Describe how you would set up a basic CI pipeline for a new project.
+    lookingFor:
+      - Understanding of CI fundamentals
+      - Basic pipeline configuration knowledge
+    expectedDurationMinutes: 8
+working:
+  - id: devops_work_1
+    text:
+      Tell me about a deployment pipeline you've built. What stages did it
+      include?
+    followUps:
+      - How did you handle failures?
+      - What monitoring did you add?
+    lookingFor:
+      - End-to-end pipeline experience
+      - Infrastructure as code awareness
+    expectedDurationMinutes: 10
+practitioner:
+  - id: devops_pract_1
+    text: How have you improved deployment practices in your team?
+    followUps:
+      - How did you measure improvement?
+    lookingFor:
+      - DevOps leadership
+      - Metrics-driven improvement
+    expectedDurationMinutes: 8
+expert:
+  - id: devops_expert_1
+    text: How have you shaped DevOps practices across an organization?
+    followUps:
+      - What cultural changes did you drive?
+    lookingFor:
+      - Organizational DevOps transformation
+      - Culture change leadership
+    expectedDurationMinutes: 10

package/examples/questions/skills/full_stack_development.yaml

@@ -0,0 +1,47 @@
+# yaml-language-server: $schema=https://schema.forwardimpact.team/json/skill-questions.schema.json
+
+awareness:
+  - id: fs_aware_1
+    text: What layers of a typical web application are you familiar with?
+    lookingFor:
+      - Basic understanding of frontend, backend, database
+      - Awareness of how layers interact
+    expectedDurationMinutes: 5
+foundational:
+  - id: fs_found_1
+    text:
+      Walk me through building a simple feature that touches the UI, API, and
+      database.
+    lookingFor:
+      - Understanding of full-stack flow
+      - Basic implementation across layers
+    expectedDurationMinutes: 10
+working:
+  - id: fs_work_1
+    text:
+      Describe a complete feature you delivered end-to-end. How did you approach
+      each layer?
+    followUps:
+      - What challenges did you face?
+    lookingFor:
+      - Independent full-stack delivery
+      - Pragmatic technology choices
+    expectedDurationMinutes: 10
+practitioner:
+  - id: fs_pract_1
+    text:
+      How do you rapidly deliver complete solutions without depending on
+      specialists?
+    followUps:
+      - How do you handle areas outside your expertise?
+    lookingFor:
+      - Speed of end-to-end delivery
+      - Self-sufficiency across the stack
+    expectedDurationMinutes: 10
+expert:
+  - id: fs_expert_1
+    text: How do you enable rapid full-stack delivery across teams?
+    lookingFor:
+      - Organizational full-stack enablement
+      - Removing specialist dependencies at scale
+    expectedDurationMinutes: 10

package/examples/questions/skills/sre_practices.yaml

@@ -0,0 +1,43 @@
+# yaml-language-server: $schema=https://schema.forwardimpact.team/json/skill-questions.schema.json
+
+awareness:
+  - id: sre_aware_1
+    text: What do you understand by SLIs, SLOs, and error budgets?
+    lookingFor:
+      - Basic SRE concepts understanding
+      - Awareness of reliability metrics
+    expectedDurationMinutes: 5
+foundational:
+  - id: sre_found_1
+    text: How would you set up basic monitoring and alerting for a service?
+    lookingFor:
+      - Understanding of observability basics
+      - Experience with monitoring tools
+    expectedDurationMinutes: 8
+working:
+  - id: sre_work_1
+    text:
+      Describe how you've handled an incident in production. What was your
+      process?
+    followUps:
+      - What did you learn from it?
+    lookingFor:
+      - Incident response experience
+      - Post-incident improvement
+    expectedDurationMinutes: 10
+practitioner:
+  - id: sre_pract_1
+    text: How do you balance reliability with feature velocity in your team?
+    lookingFor:
+      - Error budget management
+      - Pragmatic reliability decisions
+    expectedDurationMinutes: 8
+expert:
+  - id: sre_expert_1
+    text:
+      How have you established reliability culture and practices across an
+      organization?
+    lookingFor:
+      - Organizational reliability leadership
+      - Systematic reliability improvement
+    expectedDurationMinutes: 10

package/examples/questions/skills/stakeholder_management.yaml

@@ -0,0 +1,48 @@
+# yaml-language-server: $schema=https://schema.forwardimpact.team/json/skill-questions.schema.json
+
+awareness:
+  - id: stk_aware_1
+    text:
+      Who are the key stakeholders you work with and how do you keep them
+      informed?
+    lookingFor:
+      - Stakeholder identification
+      - Basic communication practices
+    expectedDurationMinutes: 5
+foundational:
+  - id: stk_found_1
+    text:
+      How do you set expectations with stakeholders about timelines and
+      deliverables?
+    lookingFor:
+      - Expectation management
+      - Proactive communication
+    expectedDurationMinutes: 5
+working:
+  - id: stk_work_1
+    text:
+      Describe a situation where you had to manage conflicting stakeholder
+      priorities.
+    followUps:
+      - How did you resolve it?
+    lookingFor:
+      - Conflict navigation
+      - Prioritization skills
+    expectedDurationMinutes: 8
+practitioner:
+  - id: stk_pract_1
+    text:
+      How do you build trust with senior stakeholders and influence their
+      decisions?
+    lookingFor:
+      - Executive relationship building
+      - Influence without authority
+    expectedDurationMinutes: 10
+expert:
+  - id: stk_expert_1
+    text:
+      How do you manage complex stakeholder landscapes across an organization?
+    lookingFor:
+      - Enterprise stakeholder management
+      - Political navigation
+    expectedDurationMinutes: 10

package/examples/questions/skills/team_collaboration.yaml

@@ -0,0 +1,42 @@
+# yaml-language-server: $schema=https://schema.forwardimpact.team/json/skill-questions.schema.json
+
+awareness:
+  - id: tc_aware_1
+    text: How do you work with your team to complete shared tasks?
+    lookingFor:
+      - Basic teamwork skills
+      - Communication practices
+    expectedDurationMinutes: 5
+foundational:
+  - id: tc_found_1
+    text:
+      Describe how you've helped a teammate when they were stuck on a problem.
+    lookingFor:
+      - Supportive collaboration
+      - Knowledge sharing
+    expectedDurationMinutes: 5
+working:
+  - id: tc_work_1
+    text: How do you facilitate effective collaboration within your team?
+    followUps:
+      - How do you handle remote collaboration?
+    lookingFor:
+      - Active collaboration facilitation
+      - Team enablement
+    expectedDurationMinutes: 8
+practitioner:
+  - id: tc_pract_1
+    text: Describe how you've built high-performing team dynamics.
+    lookingFor:
+      - Team building expertise
+      - Handling interpersonal challenges
+    expectedDurationMinutes: 10
+expert:
+  - id: tc_expert_1
+    text:
+      How do you create collaborative culture across multiple teams or an
+      organization?
+    lookingFor:
+      - Cross-team collaboration leadership
+      - Organizational culture shaping
+    expectedDurationMinutes: 10

package/examples/questions/skills/technical_writing.yaml

@@ -0,0 +1,42 @@
+# yaml-language-server: $schema=https://schema.forwardimpact.team/json/skill-questions.schema.json
+
+awareness:
+  - id: tw_aware_1
+    text: How do you approach documenting your code and work?
+    lookingFor:
+      - Basic documentation habits
+      - Understanding of documentation importance
+    expectedDurationMinutes: 5
+foundational:
+  - id: tw_found_1
+    text: What makes a good README file? Walk me through what you'd include.
+    lookingFor:
+      - README best practices
+      - Reader-centric documentation
+    expectedDurationMinutes: 5
+working:
+  - id: tw_work_1
+    text:
+      How do you write technical specifications that enable others to implement
+      features?
+    followUps:
+      - How detailed do you go?
+    lookingFor:
+      - Spec writing skills
+      - Communication of technical requirements
+    expectedDurationMinutes: 8
+practitioner:
+  - id: tw_pract_1
+    text:
+      How do you establish documentation standards and practices in your team?
+    lookingFor:
+      - Documentation leadership
+      - Spec-driven development advocacy
+    expectedDurationMinutes: 8
+expert:
+  - id: tw_expert_1
+    text: How do you create organizational documentation culture and systems?
+    lookingFor:
+      - Enterprise documentation strategy
+      - Knowledge management systems
+    expectedDurationMinutes: 10

package/examples/self-assessments.yaml

@@ -0,0 +1,64 @@
+# yaml-language-server: $schema=https://schema.forwardimpact.team/json/self-assessments.schema.json
+
+- id: example_mid_swe
+  skillLevels:
+    architecture_design: working
+    code_quality: working
+    devops: foundational
+    ai_augmented_development: foundational
+    technical_debt_management: foundational
+    lean_thinking: awareness
+    data_modeling: awareness
+    stakeholder_management: awareness
+    technical_writing: foundational
+    ai_literacy: foundational
+    service_management: awareness
+  behaviourMaturities:
+    precise_communication: developing
+    relentless_curiosity: developing
+    outcome_ownership: developing
+    polymathic_knowledge: emerging
+    systems_thinking: developing
+
+# Example: Senior Data Engineer
+- id: example_senior_de
+  skillLevels:
+    data_modeling: practitioner
+    data_integration: practitioner
+    architecture_design: working
+    code_quality: working
+    devops: working
+    cloud_platforms: working
+    ai_literacy: working
+    stakeholder_management: foundational
+    technical_writing: foundational
+    ai_augmented_development: foundational
+    lean_thinking: foundational
+  behaviourMaturities:
+    precise_communication: practicing
+    relentless_curiosity: practicing
+    outcome_ownership: practicing
+    polymathic_knowledge: developing
+    systems_thinking: practicing
+
+# Example: Data Scientist - R&D Focus
+- id: example_ds_rd
+  skillLevels:
+    model_development: working
+    data_analysis: working
+    statistical_modeling: working
+    data_modeling: foundational
+    ai_evaluation: working
+    technical_writing: foundational
+    business_immersion: foundational
+    code_quality: foundational
+    stakeholder_management: awareness
+    ai_literacy: working
+    multi_audience_communication: foundational
+    service_management: awareness
+  behaviourMaturities:
+    precise_communication: developing
+    relentless_curiosity: practicing
+    outcome_ownership: developing
+    polymathic_knowledge: developing
+    systems_thinking: developing

package/examples/stages.yaml

@@ -0,0 +1,139 @@
+# yaml-language-server: $schema=https://schema.forwardimpact.team/json/stages.schema.json
+
+- id: specify
+  name: Specify
+  emojiIcon: "🎯"
+  description:
+    Your primary task is to define WHAT users need and WHY, not how to build it.
+    Gather requirements, write user stories, and define acceptance criteria.
+  handoffs:
+    - targetStage: specify
+      label: Refine Spec
+      prompt: Refine spec.md with more detail or clarity.
+    - targetStage: specify
+      label: Alternative Spec
+      prompt: Create an alternative spec.md exploring a different approach.
+    - targetStage: plan
+      label: Create Plan
+      prompt: Create plan.md based on spec.md.
+  constraints:
+    - Do not make code edits or execute commands
+    - Focus on WHAT users need and WHY, not HOW to implement
+    - Write specifications as markdown files under specs/[feature-name]/spec.md
+    - Mark ambiguities with [NEEDS CLARIFICATION]; ask the user; do not guess
+    - No technology choices, APIs, or code structure in specifications
+  entryCriteria: []
+  exitCriteria:
+    - spec.md exists with user stories and acceptance criteria
+    - No unresolved [NEEDS CLARIFICATION] markers in spec.md
+
+- id: plan
+  name: Plan
+  emojiIcon: "📐"
+  description:
+    Your primary task is to define HOW to build the solution. Make technology
+    choices, design architecture, define contracts and data models.
+  handoffs:
+    - targetStage: plan
+      label: Refine Plan
+      prompt: Refine plan.md with more detail or clarity.
+    - targetStage: plan
+      label: Alternative Plan
+      prompt: Create an alternative plan.md exploring a different approach.
+    - targetStage: code
+      label: Start Coding
+      prompt: Implement the tasks defined in plan.md.
+  constraints:
+    - Do not make code edits or execute commands
+    - Every technology choice must trace back to a specific requirement
+    - Write plans as markdown files under specs/[feature-name]/plan.md
+    - Define contracts and data models before implementation details
+    - Document rationale for architectural decisions
+  entryCriteria:
+    - spec.md exists with user stories and acceptance criteria
+    - No unresolved [NEEDS CLARIFICATION] markers in spec.md
+  exitCriteria:
+    - plan.md exists with technology choices and architecture
+    - Contracts and data models defined where applicable
+    - No unresolved [NEEDS CLARIFICATION] markers in plan.md
+
+- id: code
+  name: Code
+  emojiIcon: "💻"
+  description:
+    Your primary task is to implement the solution. Write code, write tests, and
+    iterate until the implementation is complete.
+  handoffs:
+    - targetStage: review
+      label: Request Review
+      prompt: Review the implemented changes.
+  constraints:
+    - Implement one task at a time, verify before moving on
+    - Write tests alongside implementation
+    - Track progress with the todo tool
+  entryCriteria:
+    - spec.md exists with user stories and acceptance criteria
+    - plan.md exists with technology choices and architecture
+    - No unresolved [NEEDS CLARIFICATION] markers in plan.md
+  exitCriteria:
+    - Implementation complete according to plan.md
+    - Tests written and passing
+    - Self-review completed
+
+- id: review
+  name: Review
+  emojiIcon: "🔍"
+  description:
+    Your primary task is to verify the implementation works correctly. Run the
+    application, test against acceptance criteria, document findings.
+  handoffs:
+    - targetStage: code
+      label: Request Changes
+      prompt: Address the findings in review.md.
+    - targetStage: plan
+      label: Needs Re-planning
+      prompt: Update plan.md to address issues found in review.md.
+    - targetStage: deploy
+      label: Deploy
+      prompt: Deploy the approved changes.
+  constraints:
+    - Do not make code edits
+    - Write review findings as markdown under specs/[feature-name]/review.md
+    - Prioritize actionable feedback over exhaustive lists
+    - Track findings and required changes with the todo tool
+    - Run the application locally and verify changes work as expected
+    - Test user-facing functionality against acceptance criteria
+  entryCriteria:
+    - Implementation complete according to plan.md
+    - Tests written and passing
+    - Self-review completed
+  exitCriteria:
+    - Application runs locally without errors
+    - Changes verified against acceptance criteria through manual testing
+    - No blocking issues identified in review
+    - Review approved
+
+- id: deploy
+  name: Deploy
+  emojiIcon: "🚀"
+  description:
+    Your primary task is to ship the changes to production. Push code, monitor
+    CI/CD workflows, and verify successful deployment.
+  handoffs:
+    - targetStage: code
+      label: Fix Pipeline
+      prompt: Fix the failing workflow issues identified during deployment.
+  constraints:
+    - Use git push to deploy changes
+    - Use gh CLI to monitor triggered workflows (gh run list, gh run watch)
+    - Do not make code edits; hand off to code stage if fixes are needed
+    - Verify all workflows complete successfully before considering deployment
+      done
+  entryCriteria:
+    - Application runs locally without errors
+    - Changes verified against acceptance criteria through manual testing
+    - No blocking issues identified in review
+    - Review approved
+  exitCriteria:
+    - All triggered workflows are green
+    - Deployment verified in target environment

package/examples/tracks/_index.yaml

@@ -0,0 +1,5 @@
+# Auto-generated index for browser loading
+# Do not edit manually - regenerate with: npx pathway --generate-index
+files:
+  - platform
+  - sre

package/examples/tracks/platform.yaml

@@ -0,0 +1,49 @@
+# yaml-language-server: $schema=https://schema.forwardimpact.team/json/track.schema.json
+
+name: Platform
+
+# Shared content (used by both human job descriptions and agent profiles)
+description:
+  Internal tooling and infrastructure focus, building shared capabilities that
+  enable other engineering teams. Treats the platform as a product with
+  developers as customers.
+roleContext:
+  In this platform-focused role, you will build internal tooling and shared
+  infrastructure that enables other engineering teams to be more productive. You
+  will treat the platform as a product—conducting user research, building golden
+  paths, and optimizing for developer experience.
+
+# Derivation inputs - used by both human and agent profiles
+skillModifiers:
+  delivery: 1
+  business: 1
+  reliability: -1
+behaviourModifiers:
+  systems_thinking: 1
+  precise_communication: 1
+assessmentWeights:
+  skillWeight: 0.6
+  behaviourWeight: 0.4
+
+# Agent-specific content
+agent:
+  identity: |
+    You are a Platform {roleTitle} agent. Your primary focus is 
+    building self-service capabilities that enable other engineers.
+  priority: |
+    Developer experience is paramount. You design golden paths, maintain 
+    backward compatibility, and document everything. Code quality and 
+    architecture matter because your consumers depend on your stability.
+
+    Every API change must consider developer experience. Treat breaking 
+    changes with extreme caution—your consumers build on your stability.
+  beforeMakingChanges:
+    - Understand the existing architecture and patterns
+    - Identify test coverage requirements
+    - Consider backward compatibility implications
+    - Plan documentation updates
+  constraints:
+    - Maintain backward compatibility
+    - Document breaking changes with migration guides
+    - Test all changes against real consumer use cases
+    - Design for Day 50, not just Day 1