framework

What This Skill Does

The framework skill serves as the central brain for developers using the SpecWeave framework within their AI-assisted coding environment. It encodes the core philosophy of spec-driven development, ensuring that every feature increment is documented, planned, and executed according to strict project standards. The skill helps agents navigate the increment lifecycle—from initial specification and task breakdown to validation and final closure—ensuring that the source of truth (the living documentation) remains synchronized with the actual codebase. It enforces naming conventions, directory structure requirements, and the mandatory use of YAML frontmatter in spec files, acting as a guardrail against architectural drift and documentation rot.

Installation

You can integrate this skill into your OpenClaw environment by executing the following command: clawhub install openclaw/skills/skills/anton-abyzov/sw-framework

Use Cases

• Project Onboarding: Use this skill when joining a new repository to understand the existing increment history and documentation structure.
• Feature Planning: Invoke the skill when starting a new increment to ensure your spec.md and tasks.md files comply with the framework requirements.
• Lifecycle Management: Use the skill to verify that you are following the correct sequence of /sw commands for planning, executing, and closing increments.
• Debugging Sync Issues: If your documentation isn't updating properly, use the framework skill to diagnose missing frontmatter or structural issues in your increment folders.
• Naming Enforcement: Use it to validate that your proposed increment names are descriptive and kebab-case compliant before creating your workspace.

Example Prompts

1. "I'm starting a new feature to implement OIDC authentication. Can you help me generate the spec.md frontmatter for a 2-level structure with project 'security-auth' and board 'identity-team'?"
2. "Review my current task directory. Are there any increments that violate the naming convention or missing mandatory files like metadata.json?"
3. "Explain the increment lifecycle for a hotfix. Do I need to include a plan.md file for a simple dependency update?"

Tips & Limitations

• Strict Adherence: The framework requires the project key in every spec.md. Always prioritize this field for traceability.
• Automated Hooks: Take advantage of the living docs features; the skill is most effective when your environment is configured to run the framework sync hooks on save.
• Scope: This skill is specifically designed for SpecWeave. It will not provide general coding assistance for languages like Python or Rust unless the context involves modifying existing increments.
• Naming: Avoid generic numbers. If you use 0005 without a description, the skill will flag it as non-compliant.