Skip to content
Back to skills

Specify

ASecurity

Run ICM stage 01 - turn a feature request into a spec change, a plan and a techspec

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 26, 2026
ai-agents

Security analysis

A100/100

Scanned September 26, 2026

npx -y skills add andyrids/icm-spec --skill specify --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Specify?

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

Security grade badge for Specify
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/andyrids-specify/badge)](https://www.skillsdirectory.com/skills/andyrids-specify)

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
---
name: specify
description: Run ICM stage 01 - turn a feature request into a spec change, a plan and a techspec
disable-model-invocation: true
---

# ICM stage 01 - specification

The argument is the feature request. If it is empty, ask for one before doing anything else.

1. Read `CONTEXT.md` at the repository root, then `ICM/process-plan/CONTEXT.md`, then
   `ICM/process-plan/stages/01-specification/CONTEXT.md`. If any of these is missing, stop and
   suggest `/icm:init`.
2. Execute the stage contract exactly as written - it defines the inputs, process and outputs.
3. Stop at the workspace's review gate: present the spec change, the plan and the techspec for
   explicit user acceptance before any implementation begins. `/icm:implement` is the next step
   once accepted.

$ARGUMENTS

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.