@forwardimpact/pathway 0.1.0 → 0.3.0

package/examples/agents/.claude/skills/technical-writing/SKILL.md

@@ -1,129 +0,0 @@
----
-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.
----
-
-# Technical Writing
-
-## When to use this skill
-
-Use this skill when:
-
-- Writing README files
-- Creating API documentation
-- Writing technical specifications
-- Documenting code and systems
-- Creating guides and tutorials
-
-## Writing Principles
-
-### Clarity First
-
-- Use simple, direct language
-- One idea per sentence
-- Active voice over passive
-- Avoid jargon unless defined
-- Be specific, not vague
-
-### Know Your Audience
-
-- What do they already know?
-- What do they need to accomplish?
-- What's their skill level?
-- What questions will they have?
-
-### Structure for Scanning
-
-- Lead with the most important information
-- Use headings and subheadings
-- Keep paragraphs short
-- Use lists for multiple items
-- Highlight key terms
-
-## Document Types
-
-### README
-
-- What is this project?
-- How do I get started?
-- How do I use it?
-- Where do I get help?
-
-### API Documentation
-
-- Endpoint description
-- Parameters and types
-- Request/response examples
-- Error codes and handling
-
-### Technical Specification
-
-- Problem statement
-- Proposed solution
-- Alternatives considered
-- Implementation plan
-
-### Tutorial
-
-- Clear learning objective
-- Prerequisites listed
-- Step-by-step instructions
-- Expected outcomes shown
-
-## README Template
-
-```markdown
-# Project Name
-
-Brief description of what this project does.
-
-## Getting Started
-
-### Prerequisites
-
-- Required software and versions
-
-### Installation
-
-Step-by-step installation instructions.
-
-### Quick Start
-
-Minimal example to get running.
-
-## Usage
-
-Common use cases with examples.
-
-## Contributing
-
-How to contribute to the project.
-
-## License
-
-License information.
-```
-
-## Code Examples
-
-Good examples are:
-
-- Complete and runnable
-- Minimal but realistic
-- Copy-pasteable
-- Annotated with comments
-- Tested and verified
-
-## Technical Writing Checklist
-
-- [ ] Purpose is clear in first paragraph
-- [ ] Audience is identified
-- [ ] Prerequisites are listed
-- [ ] Examples are tested and work
-- [ ] Technical terms are defined
-- [ ] Structure supports scanning
-- [ ] No ambiguous pronouns
-- [ ] Updated when code changes

package/examples/tracks/manager.yaml

@@ -1,53 +0,0 @@
-# Track: Engineering Manager
-# People and delivery leadership
-
-name: Engineering Manager
-
-# Track type - management track (professional defaults to false)
-isManagement: true
-
-# Shared content (used by both human job descriptions and agent profiles)
-description:
-  People and delivery leadership, focusing on team effectiveness, career
-  development, and organizational outcomes. Creates space for curiosity and
-  experimentation; models ownership behaviours.
-roleContext:
-  In this leadership role, you will focus on people and delivery management,
-  driving team effectiveness and career development. You will create space for
-  curiosity and experimentation while modeling ownership behaviours and ensuring
-  organizational outcomes are achieved.
-
-# Derivation inputs - used by both human and agent profiles
-skillModifiers:
-  business: 2
-  people: 2
-  reliability: -1
-  delivery: -2
-  scale: -2
-behaviourModifiers:
-  polymathic_knowledge: 1
-assessmentWeights:
-  skillWeight: 0.4
-  behaviourWeight: 0.6
-
-# Agent-specific content
-agent:
-  coreInstructions: |
-    You are a {specialization} leadership support agent. Your primary 
-    focus is supporting engineering managers with team effectiveness, 
-    process design, and communication.
-
-    People and process over direct implementation. You help create space 
-    for curiosity and experimentation, model ownership behaviors, and 
-    remove organizational friction.
-
-    Before making changes:
-    1. Consider team dynamics and individual growth
-    2. Think about systemic improvements over individual fixes
-    3. Focus on enabling others rather than doing directly
-
-    Your role is to support engineering judgment, not replace it.
-  constraints:
-    - Focus on enabling and empowering rather than doing directly
-    - Consider long-term team health over short-term fixes
-    - Support engineering judgment, don't replace it