specrate_skill

Overview

This skill manages specifications and changes using a structured specrate workflow. It helps propose, plan, implement, amend, fix, show status for, and archive spec changes while keeping all artifacts inside a single repository folder. Use it when you need controlled, auditable spec evolution tied to your codebase.

How this skill works

The skill inspects the user's intent and maps it to a single specrate action (show status, propose, plan, implement, amend, fix, or archive). For mixed or unclear intents it breaks the request into discrete actions, asks clarifying questions, and executes steps one at a time. All created or updated artifacts are placed under .specrate/ at the repo root to maintain workspace consistency.

When to use it

• You want an auditable proposal for a new specification change
• You need to plan or implement a previously proposed change
• You must amend or correct an existing change or spec
• You want a current status report of specs and active changes
• You need to archive implemented changes or reconcile specs with the codebase

Best practices

• Read the core discipline and principles before acting to understand workflow expectations
• Keep each user intent targeted to one action; split complex requests into steps
• Confirm before creating or modifying .specrate/ artifacts to avoid unwanted edits
• Provide clear metadata (owner, motivation, scope, and timeline) when proposing changes
• When ambiguous, choose from concise options rather than freeform responses to speed decisions

Example use cases

• Create a new change proposal with motivation, acceptance criteria, and initial plan
• Show the current status of all active proposals and which are in planning or implementation
• Amend an existing change to update scope or acceptance criteria based on feedback
• Plan a proposed change into concrete tasks and assign owners and timelines
• Implement a planned change and move related artifacts into archive when complete