specify is agent-read markdown (skill) from papadopouloskyriakos/agentic-chatops: Phase B of greenfield project bootstrap. Interview the operator to produce PROJECT.json + PROJECT.md + spec/NNN-*/requirements.md (EARS-only) + acceptance/*.feature scenarios. Iterates until ears-lint.py passes..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# /specify — interview-driven greenfield specification
You are a senior product/spec author. The operator just typed `/specify` because they want to bootstrap a new project. They have an idea but no spec yet.
## Your job
Produce these artifacts in the current project directory:
1. `PROJECT.md` — one-page charter (vision, success metrics, owners) in plain English
2. `PROJECT.json` — machine-readable companion (per `<bootstrap-pack>/templates/PROJECT.schema.json`)
3. `spec/001-<slug>/requirements.md` — EARS-only requirements with REQ-NNN IDs
4. `spec/001-<slug>/acceptance/*.feature` — at least one Gherkin scenario per REQ-NNN
## Interview style
- Use **AskUserQuestion**. Single-purpose questions, 2-4 options each.
- Don't ask obvious questions. Dig into the hard parts the operator hasn't considered.
- Cover: target users, success criteria, scope boundaries, integrations, data model, failure modes, non-functional requirements (latency, scale, security, compliance).
- Keep going until you've covered all 6 dimensions above.
## EARS notation discipline
Every line in `requirements.md` MUST match one of the 5 patterns (case-sensitive, mind the period):
| Pattern | Template |
…
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
GET https://markdownregistry.com/api/v1/artifacts/art_kf5kxuoa23427duv
GET https://markdownregistry.com/api/v1/resolve?ref=papadopouloskyriakos/agentic-chatops/specify
GET https://markdownregistry.com/api/v1/blob/6f4dd32dad2af12bcd61a8262c0a0a461b6e9d1d013b46fe3412a5dce380fc49
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
papadopouloskyriakos/agentic-chatops · bootstrap-pack/.claude/skills/tasks/SKILL.md · Phase E of greenfield project bootstrap. Atomize design.md + contracts into tasks.json with files_owned + dependencies…
papadopouloskyriakos/agentic-chatops · openclaw/skills/codegraph-lookup/SKILL.md · Query code graph database for function callers, callees, dependencies, and dead code in CubeOS and MeshSat repos.
papadopouloskyriakos/agentic-chatops · openclaw/skills/correlated-triage/SKILL.md · When multiple hosts alert simultaneously (burst), create a master YouTrack issue, run per-host triage, link children…
papadopouloskyriakos/agentic-chatops · openclaw/skills/error-propagation/SKILL.md · Structured error reporting format for triage failures — ERROR_CONTEXT format so next tier can resume without re-doing…
papadopouloskyriakos/agentic-chatops · openclaw/skills/escalate-to-claude/SKILL.md · Escalate a YouTrack issue to Claude Code (Tier 2) for CODE IMPLEMENTATION ONLY. Use ONLY when someone explicitly asks…
papadopouloskyriakos/agentic-chatops · openclaw/skills/exec-safety/SKILL.md · Blocked command list for exec tool — commands that must NEVER be executed, even if asked.
jantichy/claude · skills/specify/SKILL.md · Skill se použije, když uživatel zadá "/specify" (volitelně s tématem), nebo chce z nápadu udělat zadání – produktovou…
dayfinggg/openai-codex-agent-skills · codex/skills/specify/SKILL.md · Consolidate accepted requirements into a testable implementation specification. Use when asked for a specification of…