Skip to content
Back to skills

Specrate

ASecurity

Manage specs and changes to specs in a structured workflow for proposing, planning, implementing, and archiving changes.

  • 7 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added June 6, 2026
businessgitdocumentation

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned June 6, 2026

npx -y skills add mediar-ai/skillhubz --skill specrate --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Specrate?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Specrate
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mediar-ai-specrate/badge)](https://www.skillsdirectory.com/skills/mediar-ai-specrate)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
# Specrate

Manage specs and changes to specs in a structured workflow for proposing, planning, implementing, and archiving changes.

## Prerequisites

- Git repository
- Understanding of spec-driven development

## Instructions

### Core Actions

Based on user intent, follow the appropriate action:

| Intent | Action |
|--------|--------|
| Show current status | SHOW-STATUS |
| Propose a new change | PROPOSE-CHANGE |
| Amend an existing change | AMEND-CHANGE |
| Plan a proposed change | PLAN-CHANGE |
| Implement a planned change | IMPLEMENT-CHANGE |
| Archive an implemented change | ARCHIVE-CHANGE |
| Fix a spec according to codebase | FIX-SPEC |

### Workflow

```
Propose → Plan → Implement → Archive
```

Each step has validation and documentation requirements.

### Directory Structure

All specrate artifacts reside in `.specrate/` at repository root:

```
.specrate/
├── specs/           # Current specifications
├── changes/         # Proposed and active changes
│   ├── proposed/
│   ├── planned/
│   └── implementing/
└── archive/         # Completed changes
```

### Handling Ambiguous Requests

- If intent mixes multiple actions: break down and confirm
- If intent is ambiguous (e.g., "update the spec"): ask clarifying questions with options

## Guidelines

1. Always ask for clarifications if needed
2. Ensure workspace remains consistent after each step
3. All artifacts MUST reside in `.specrate/` folder
4. Do NOT create auxiliary documents outside `.specrate/`
5. Provide concise options when asking for clarifications

## Notes

- Designed for structured change management
- Supports full change lifecycle tracking
- Maintains audit trail of all spec modifications

Source: rickygao/specrate

Files in this skill

  • manifest.json340 B
  • skill.md1.7 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.