@forwardimpact/pathway 0.1.0 → 0.2.0

package/examples/agents/.claude/skills/architecture-design/SKILL.md

@@ -8,14 +8,66 @@ description: |
 
 # Architecture & Design
 
-## When to use this skill
+## Stage Guidance
 
-Use this skill when:
+### Plan Stage
 
-- Designing new systems or major features
-- Evaluating architectural options and trade-offs
-- Making decisions about code organization and structure
-- Reviewing or improving existing architecture
+**Focus:** Understand requirements and identify key architectural decisions.
+Document trade-offs and design rationale.
+
+**Activities:**
+
+- Clarify functional and non-functional requirements
+- Identify constraints (existing systems, team skills, timeline)
+- Document key decisions and trade-offs
+- Design for anticipated change
+
+**Ready for Code when:**
+
+- [ ] Requirements are clearly understood
+- [ ] Key decisions are documented with rationale
+- [ ] Trade-offs are explicit
+- [ ] Failure modes are considered
+
+### Code Stage
+
+**Focus:** Implement architecture with clear boundaries and interfaces. Ensure
+components can evolve independently.
+
+**Activities:**
+
+- Define clear interfaces between components
+- Implement with appropriate patterns
+- Document design decisions in code
+- Test architectural boundaries
+
+**Ready for Review when:**
+
+- [ ] Dependencies are minimal and explicit
+- [ ] Interfaces are well-defined
+- [ ] Design patterns are documented
+- [ ] Architecture tests pass
+
+### Review Stage
+
+**Focus:** Validate architecture meets requirements and is maintainable. Ensure
+scalability and security are addressed.
+
+**Activities:**
+
+- Verify architecture meets requirements
+- Review for scalability concerns
+- Check security implications
+- Validate documentation completeness
+
+**Ready for Complete when:**
+
+- [ ] Scalability requirements are addressed
+- [ ] Security implications are reviewed
+- [ ] Architecture is documented
+- [ ] Design is maintainable
+
+## Reference
 
 ## Design Process
 
@@ -76,13 +128,3 @@ Good architecture accommodates change:
 - REST: Synchronous, request-response
 - Event-driven: Asynchronous, loose coupling
 - gRPC: Efficient, strongly typed
-
-## Architecture Checklist
-
-- [ ] Requirements are clearly understood
-- [ ] Key decisions are documented with rationale
-- [ ] Trade-offs are explicit
-- [ ] Failure modes are considered
-- [ ] Scalability requirements are addressed
-- [ ] Security implications are reviewed
-- [ ] Dependencies are minimal and explicit

package/examples/agents/.claude/skills/cloud-platforms/SKILL.md

@@ -8,15 +8,67 @@ description: |
 
 # Cloud Platforms
 
-## When to use this skill
+## Stage Guidance
 
-Use this skill when:
+### Plan Stage
 
-- Deploying applications to cloud environments
-- Selecting appropriate cloud services
-- Configuring cloud infrastructure
-- Optimizing cloud costs and performance
-- Implementing cloud security best practices
+**Focus:** Select appropriate cloud services and design for availability,
+security, and cost efficiency.
+
+**Activities:**
+
+- Identify service requirements
+- Select appropriate cloud services
+- Plan for high availability
+- Consider security and cost
+
+**Ready for Code when:**
+
+- [ ] Service selection matches requirements
+- [ ] Availability approach planned
+- [ ] Security model defined
+- [ ] Cost controls considered
+
+### Code Stage
+
+**Focus:** Implement cloud infrastructure with security best practices. Use
+infrastructure as code for reproducibility.
+
+**Activities:**
+
+- Define infrastructure as code
+- Configure security groups and IAM
+- Set up monitoring and alerting
+- Implement deployment automation
+
+**Ready for Review when:**
+
+- [ ] Multi-AZ deployment for availability
+- [ ] Security groups properly configured
+- [ ] IAM follows least privilege
+- [ ] Data encrypted at rest and in transit
+- [ ] Infrastructure defined as code
+
+### Review Stage
+
+**Focus:** Validate security, availability, and operational readiness. Ensure
+cost controls are in place.
+
+**Activities:**
+
+- Verify security configuration
+- Test availability and failover
+- Review cost projections
+- Validate monitoring coverage
+
+**Ready for Complete when:**
+
+- [ ] Security review completed
+- [ ] Monitoring and alerting in place
+- [ ] Cost controls established
+- [ ] Operational runbooks exist
+
+## Reference
 
 ## Service Categories
 
@@ -77,14 +129,3 @@ Use this skill when:
 - Leverage spot/preemptible instances for fault-tolerant work
 - Set up billing alerts and budgets
 - Delete unused resources
-
-## Cloud Checklist
-
-- [ ] Service selection matches requirements
-- [ ] Multi-AZ deployment for availability
-- [ ] Security groups properly configured
-- [ ] IAM follows least privilege
-- [ ] Data encrypted at rest and in transit
-- [ ] Monitoring and alerting in place
-- [ ] Cost controls established
-- [ ] Infrastructure defined as code

package/examples/agents/.claude/skills/code-quality-review/SKILL.md

@@ -8,14 +8,66 @@ description: |
 
 # Code Quality & Review
 
-## When to use this skill
+## Stage Guidance
 
-Use this skill when:
+### Plan Stage
 
-- Reviewing code for quality issues
-- Checking code against best practices
-- Conducting or assisting with code reviews
-- Verifying AI-generated code before committing
+**Focus:** Understand code review scope and establish review criteria. Consider
+what quality standards apply.
+
+**Activities:**
+
+- Identify code review scope
+- Understand applicable standards
+- Plan review approach
+- Consider risk level
+
+**Ready for Code when:**
+
+- [ ] Review scope is clear
+- [ ] Standards are understood
+- [ ] Review approach is planned
+- [ ] Risk level is assessed
+
+### Code Stage
+
+**Focus:** Write clean, maintainable, tested code. Follow project conventions
+and ensure adequate coverage.
+
+**Activities:**
+
+- Write readable, well-structured code
+- Add appropriate tests
+- Follow project conventions
+- Document non-obvious logic
+
+**Ready for Review when:**
+
+- [ ] Code compiles and passes all tests
+- [ ] Changes are covered by tests
+- [ ] Code follows project conventions
+- [ ] No unnecessary complexity
+
+### Review Stage
+
+**Focus:** Verify correctness, maintainability, and adherence to standards.
+Ensure no code is shipped that isn't understood.
+
+**Activities:**
+
+- Verify code does what it claims
+- Check test coverage
+- Review for maintainability
+- Confirm style compliance
+
+**Ready for Complete when:**
+
+- [ ] No obvious security vulnerabilities
+- [ ] Error handling is appropriate
+- [ ] Documentation updated if needed
+- [ ] No code you don't fully understand
+
+## Reference
 
 ## Review Process
 
@@ -54,14 +106,3 @@ Verify consistency with project standards:
 - Consistent formatting and indentation
 - Appropriate comments for non-obvious logic
 - Documentation updated if needed
-
-## Quality Checklist
-
-- [ ] Code compiles and passes all tests
-- [ ] Changes are covered by tests
-- [ ] No obvious security vulnerabilities
-- [ ] Error handling is appropriate
-- [ ] Code follows project conventions
-- [ ] No unnecessary complexity
-- [ ] Documentation updated if needed
-- [ ] No code you don't fully understand

package/examples/agents/.claude/skills/devops-cicd/SKILL.md

@@ -8,15 +8,72 @@ description: |
 
 # DevOps & CI/CD
 
-## When to use this skill
+## Stage Guidance
 
-Use this skill when:
+### Plan Stage
 
-- Setting up or modifying CI/CD pipelines
-- Containerizing applications with Docker
-- Managing infrastructure as code
-- Troubleshooting deployment failures
-- Implementing monitoring and alerting
+**Focus:** Plan CI/CD pipeline architecture and infrastructure requirements.
+Consider deployment strategies and monitoring needs.
+
+**Activities:**
+
+- Define pipeline stages (build, test, deploy)
+- Identify infrastructure requirements
+- Plan deployment strategy (rolling, blue-green, canary)
+- Consider monitoring and alerting needs
+- Plan secret management approach
+
+**Ready for Code when:**
+
+- [ ] Pipeline architecture is documented
+- [ ] Deployment strategy is chosen and justified
+- [ ] Infrastructure requirements are identified
+- [ ] Monitoring approach is defined
+
+### Code Stage
+
+**Focus:** Implement CI/CD pipelines and infrastructure as code. Follow best
+practices for containerization and deployment automation.
+
+**Activities:**
+
+- Configure CI/CD pipeline stages
+- Implement infrastructure as code (Terraform, CloudFormation)
+- Create Dockerfiles with security best practices
+- Set up monitoring and alerting
+- Configure secret management
+- Implement deployment automation
+
+**Ready for Review when:**
+
+- [ ] Pipeline runs on every commit
+- [ ] Tests run before deployment
+- [ ] Deployments are automated
+- [ ] Infrastructure is version controlled
+- [ ] Secrets are managed securely
+- [ ] Monitoring is in place
+
+### Review Stage
+
+**Focus:** Verify pipeline reliability, security, and operational readiness.
+Ensure rollback procedures work and documentation is complete.
+
+**Activities:**
+
+- Verify pipeline runs successfully end-to-end
+- Test rollback procedures
+- Review security configurations
+- Validate monitoring and alerts
+- Check documentation completeness
+
+**Ready for Complete when:**
+
+- [ ] Pipeline is tested and reliable
+- [ ] Rollback procedure is documented and tested
+- [ ] Alerts are configured and tested
+- [ ] Runbooks exist for common issues
+
+## Reference
 
 ## CI/CD Pipeline Stages
 
@@ -83,14 +140,3 @@ CMD ["node", "server.js"]
 - Route small percentage to new version
 - Monitor for issues
 - Gradually increase traffic
-
-## DevOps Checklist
-
-- [ ] Pipeline runs on every commit
-- [ ] Tests run before deployment
-- [ ] Deployments are automated
-- [ ] Rollback procedure is documented
-- [ ] Infrastructure is version controlled
-- [ ] Secrets are managed securely
-- [ ] Monitoring is in place
-- [ ] Alerts are configured

package/examples/agents/.claude/skills/full-stack-development/SKILL.md

@@ -8,14 +8,67 @@ description: |
 
 # Full-Stack Development
 
-## When to use this skill
+## Stage Guidance
 
-Use this skill when:
+### Plan Stage
 
-- Building features that span multiple layers
-- Implementing end-to-end functionality
-- Working across frontend, backend, and infrastructure
-- Debugging issues that cross layer boundaries
+**Focus:** Design the full-stack solution architecture. Define API contracts and
+plan layer interactions.
+
+**Activities:**
+
+- Define the API contract first
+- Plan frontend and backend responsibilities
+- Design database schema
+- Plan infrastructure requirements
+
+**Ready for Code when:**
+
+- [ ] API contract is defined
+- [ ] Layer responsibilities are clear
+- [ ] Database schema is planned
+- [ ] Infrastructure approach is decided
+
+### Code Stage
+
+**Focus:** Build vertically—complete one feature end-to-end before starting
+another. Validates assumptions early.
+
+**Activities:**
+
+- Implement API endpoints
+- Build frontend integration
+- Create database schema and queries
+- Configure infrastructure as needed
+- Test across layers
+
+**Ready for Review when:**
+
+- [ ] Frontend connects to backend correctly
+- [ ] Database schema supports the feature
+- [ ] Error handling spans all layers
+- [ ] Feature works end-to-end
+- [ ] Deployment is automated
+
+### Review Stage
+
+**Focus:** Verify integration across layers and ensure deployment readiness.
+
+**Activities:**
+
+- Test integration across all layers
+- Verify error handling end-to-end
+- Check deployment configuration
+- Review documentation
+
+**Ready for Complete when:**
+
+- [ ] Integration tests pass
+- [ ] Deployment verified
+- [ ] Documentation is complete
+- [ ] Feature is production-ready
+
+## Reference
 
 ## Technology Stack
 
@@ -79,12 +132,3 @@ Use this skill when:
 - Unit tests per layer
 - Integration tests across layers
 - End-to-end tests for critical paths
-
-## Full-Stack Checklist
-
-- [ ] API contract is defined
-- [ ] Frontend connects to backend correctly
-- [ ] Database schema supports the feature
-- [ ] Error handling spans all layers
-- [ ] Feature works end-to-end
-- [ ] Deployment is automated

package/examples/agents/.claude/skills/sre-practices/SKILL.md

@@ -8,15 +8,72 @@ description: |
 
 # Site Reliability Engineering
 
-## When to use this skill
+## Stage Guidance
 
-Use this skill when:
+### Plan Stage
 
-- Designing monitoring and alerting
-- Defining SLIs, SLOs, and error budgets
-- Handling or preparing for incidents
-- Conducting post-mortems
-- Planning for capacity and resilience
+**Focus:** Define reliability requirements, SLIs/SLOs, and observability
+strategy. Plan for resilience and capacity needs.
+
+**Activities:**
+
+- Define SLIs for key user journeys
+- Set SLOs with stakeholder agreement
+- Plan observability strategy (metrics, logs, traces)
+- Identify failure modes and resilience patterns
+- Define alerting thresholds
+
+**Ready for Code when:**
+
+- [ ] SLIs defined for key user journeys
+- [ ] SLOs set with stakeholder agreement
+- [ ] Monitoring strategy is planned
+- [ ] Failure modes are identified
+- [ ] Alerting thresholds are defined
+
+### Code Stage
+
+**Focus:** Implement observability, resilience patterns, and operational
+tooling. Build systems that fail gracefully and recover quickly.
+
+**Activities:**
+
+- Implement metrics, logging, and tracing
+- Configure alerts based on SLOs
+- Implement resilience patterns (timeouts, retries, circuit breakers)
+- Create runbooks for common issues
+- Set up error budget tracking
+
+**Ready for Review when:**
+
+- [ ] Comprehensive monitoring is in place
+- [ ] Alerts are actionable and low-noise
+- [ ] Resilience patterns are implemented
+- [ ] Runbooks exist for common issues
+- [ ] Error budget tracking is in place
+
+### Review Stage
+
+**Focus:** Verify reliability implementation meets SLOs and operational
+readiness. Ensure incident response procedures are in place.
+
+**Activities:**
+
+- Validate SLOs are measurable
+- Test failure scenarios
+- Review runbook completeness
+- Verify incident response procedures
+- Check alert quality and coverage
+
+**Ready for Complete when:**
+
+- [ ] SLOs are measurable and validated
+- [ ] Failure scenarios are tested
+- [ ] Incident response process documented
+- [ ] Post-mortem culture established
+- [ ] Disaster recovery approach is tested
+
+## Reference
 
 ## Service Level Concepts
 
@@ -104,14 +161,3 @@ Allowed unreliability: 100% - SLO
 - **Circuit breakers**: Fail fast when downstream is unhealthy
 - **Bulkheads**: Isolate failures
 - **Graceful degradation**: Partial functionality over total failure
-
-## SRE Checklist
-
-- [ ] SLIs defined for key user journeys
-- [ ] SLOs set with stakeholder agreement
-- [ ] Error budget tracking in place
-- [ ] Alerts are actionable and low-noise
-- [ ] Runbooks exist for common issues
-- [ ] Incident response process documented
-- [ ] Post-mortem culture established
-- [ ] Resilience patterns implemented

package/examples/agents/.claude/skills/technical-debt-management/SKILL.md

@@ -8,15 +8,66 @@ description: |
 
 # Technical Debt Management
 
-## When to use this skill
+## Stage Guidance
 
-Use this skill when:
+### Plan Stage
 
-- Identifying technical debt in codebases
-- Prioritizing debt for remediation
-- Deciding whether to take on new debt
-- Planning refactoring initiatives
-- Balancing debt work with feature delivery
+**Focus:** Assess technical debt and prioritize based on impact and effort.
+Decide whether to accept, defer, or address debt.
+
+**Activities:**
+
+- Identify and document technical debt
+- Assess impact and effort for each item
+- Prioritize using impact/effort matrix
+- Decide accept, defer, or address
+
+**Ready for Code when:**
+
+- [ ] Debt is documented with context
+- [ ] Impact and effort are assessed
+- [ ] Prioritization criteria are clear
+- [ ] Decision is documented
+
+### Code Stage
+
+**Focus:** Address debt incrementally while delivering features. Document
+intentional debt clearly.
+
+**Activities:**
+
+- Apply Boy Scout Rule (leave code better)
+- Refactor while adding features
+- Document new intentional debt
+- Track debt in backlog
+
+**Ready for Review when:**
+
+- [ ] Debt work is visible in planning
+- [ ] New debt is intentional and documented
+- [ ] Code quality improved where touched
+- [ ] Technical debt backlog updated
+
+### Review Stage
+
+**Focus:** Validate debt reduction and ensure new debt is intentional and
+documented.
+
+**Activities:**
+
+- Review debt reduction progress
+- Verify new debt is documented
+- Check debt backlog currency
+- Assess overall technical health
+
+**Ready for Complete when:**
+
+- [ ] Debt reduction validated
+- [ ] New debt justified and documented
+- [ ] Backlog is current
+- [ ] Metrics track debt trends
+
+## Reference
 
 ## Types of Technical Debt
 
@@ -111,13 +162,3 @@ For each debt item:
 - **Effort**: How hard to fix (T-shirt size)?
 - **Owner**: Who can address it?
 - **Plan**: When/how will it be fixed?
-
-## Technical Debt Checklist
-
-- [ ] Debt is documented with context
-- [ ] Impact and effort are assessed
-- [ ] Prioritization criteria are clear
-- [ ] Debt work is visible in planning
-- [ ] New debt is intentional and documented
-- [ ] Regular reviews of debt backlog
-- [ ] Metrics track debt trends