project-alignment
npx machina-cli add skill akaszubski/autonomous-dev/project-alignment --openclawProject Alignment Skill
Patterns for maintaining alignment with PROJECT.md goals, scope, and constraints.
When This Skill Activates
- Validating feature alignment with PROJECT.md
- Assessing project scope
- Checking architectural constraints
- Keywords: "project", "alignment", "goals", "scope"
Core Concepts
Overview
This skill provides guidance on maintaining alignment with PROJECT.md. For detailed validation patterns, see the project-alignment-validation skill.
Key Topics:
- PROJECT.md structure and semantics
- Goal alignment validation
- Scope boundary checks
- Constraint adherence
See: project-alignment-validation skill for detailed validation patterns
Progressive Disclosure
This skill uses progressive disclosure to prevent context bloat:
- Index (this file): High-level concepts (<500 lines)
- Detailed patterns: See project-alignment-validation skill
Cross-References
Related Skills:
- project-alignment-validation - Detailed validation patterns
- semantic-validation - Semantic analysis patterns
Key Takeaways
- Always validate features against PROJECT.md goals
- Check scope boundaries before implementation
- Respect architectural constraints
- Refer to project-alignment-validation skill for detailed patterns
Source
git clone https://github.com/akaszubski/autonomous-dev/blob/master/plugins/autonomous-dev/skills/archived/project-alignment/SKILL.mdView on GitHub Overview
Provides high-level guidance for keeping work in line with PROJECT.md goals, scope, and constraints. It highlights core alignment concepts and points to the project-alignment-validation skill for detailed validation patterns. The approach gates features early to prevent drift and ensures governance throughout the lifecycle.
How This Skill Works
Review feature proposals against PROJECT.md structure and semantics to verify goal alignment, scope boundaries, and constraint adherence. When issues are found, teams consult project-alignment-validation for detailed criteria, while leveraging progressive disclosure to keep context manageable.
When to Use It
- Before starting a feature, to verify alignment with PROJECT.md goals
- When assessing potential scope creep or boundary changes
- When evaluating architectural constraints for a design
- During feature reviews or PRs to ensure alignment before merge
- During onboarding to establish governance expectations
Quick Start
- Step 1: Review the PROJECT.md goals, scope, and constraints for the feature
- Step 2: Compare the plan against goals and boundaries; bookmark any gaps
- Step 3: Decide to proceed, adjust scope/design, or update PROJECT.md; escalate to project-alignment-validation if needed
Best Practices
- Always start from the PROJECT.md goals, scope, and constraints for a feature proposal
- Perform alignment checks early to avoid drift and rework
- Document any deviations with rationale and request updates if needed
- Leverage project-alignment-validation for detailed patterns and criteria
- Keep the PROJECT.md and alignment notes lightweight and up-to-date as decisions evolve
Example Use Cases
- Example 1: A new reporting feature is reviewed and proven to align with goals and stays within scope; proceed to development
- Example 2: A proposed data-retention change expands scope beyond PROJECT.md; triggers a re-scope discussion
- Example 3: A design proposes using a non-approved service; flagged and refactored to comply with constraints
- Example 4: A minor UI tweak aligns with goals; alignment approved quickly
- Example 5: Alignment found lacking during PR; team updates PROJECT.md to reflect new constraints after discussion
