How do I install the Zerg:plan skill?

Run npx skillmds@latest add tools-only/zerg-plan in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Zerg:plan skill do?

Capture complete requirements for a feature through interactive discovery. It is listed under Coding & Dev Tools on SkillMD.

Is Zerg:plan safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Zerg:plan?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Zerg:plan free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Zerg:plan?

tools-only (@tools-only) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Zerg:plan by tools-only — Agent Skill

Name: Zerg:plan
Author: tools-only

File contents

/zerg:plan

Capture complete requirements for a feature through interactive discovery.

Synopsis

/zerg:plan <feature-name> [OPTIONS]

Description

/zerg:plan starts an interactive requirements gathering session for the named feature. It creates a spec directory at .gsd/specs/<feature>/, explores the existing codebase for context, asks clarifying questions, and produces a requirements.md document for user approval.

The command follows a five-phase workflow:

Context Gathering -- Reads PROJECT.md, INFRASTRUCTURE.md, and explores the codebase to understand existing patterns and technology stack.
Requirements Elicitation -- Asks grouped clarifying questions covering problem space, functional requirements, non-functional requirements, scope boundaries, dependencies, and acceptance criteria.
Generate requirements.md -- Writes a comprehensive requirements document to .gsd/specs/<feature>/requirements.md.
Infrastructure Requirements -- Identifies any additional infrastructure needs (services, environment variables, MCP servers) and updates .gsd/INFRASTRUCTURE.md if needed.
User Approval -- Presents the requirements for review. The user responds with APPROVED, REJECTED, or specific change requests.

The feature name is sanitized to lowercase with hyphens only (a-z, 0-9, -).

Socratic Mode

With --socratic, the command uses a structured multi-round discovery process instead of a single question pass. Each round builds on the previous answers to deepen understanding.

Status Markers

The requirements document progresses through these states:

Status	Meaning
DRAFT	Still gathering requirements
REVIEW	Requirements complete, awaiting user approval
APPROVED	User approved, ready for design
REJECTED	Requirements need revision

Options

Option	Description
`<feature-name>`	Required. Name of the feature to plan
`-s`, `--socratic`	Use structured multi-round discovery mode
`--rounds N`	Number of discovery rounds in Socratic mode (default: 3, max: 5)

Examples

# Plan a feature
/zerg:plan user-auth

# Plan with Socratic discovery
/zerg:plan user-auth --socratic

# Socratic mode with 5 rounds
/zerg:plan payment-api --socratic --rounds 5

Output

On completion, the following files are created:

.gsd/
  .current-feature          # Set to the feature name
  specs/<feature>/
    requirements.md         # The requirements document
    .started                # Timestamp of when planning began

Completion Criteria

requirements.md exists with Status: APPROVED
All open questions are resolved or accepted
User has explicitly replied with "APPROVED"
Infrastructure needs are identified and documented

---name: zerg-plandescription: Capture complete requirements for a feature through interactive discovery.---# /zerg:planCapture complete requirements for a feature through interactive discovery.## Synopsis```/zerg:plan <feature-name> [OPTIONS]```## Description`/zerg:plan` starts an interactive requirements gathering session for the named feature. It creates a spec directory at `.gsd/specs/<feature>/`, explores the existing codebase for context, asks clarifying questions, and produces a `requirements.md` document for user approval.The command follows a five-phase workflow:1. **Context Gathering** -- Reads `PROJECT.md`, `INFRASTRUCTURE.md`, and explores the codebase to understand existing patterns and technology stack.2. **Requirements Elicitation** -- Asks grouped clarifying questions covering problem space, functional requirements, non-functional requirements, scope boundaries, dependencies, and acceptance criteria.3. **Generate requirements.md** -- Writes a comprehensive requirements document to `.gsd/specs/<feature>/requirements.md`.4. **Infrastructure Requirements** -- Identifies any additional infrastructure needs (services, environment variables, MCP servers) and updates `.gsd/INFRASTRUCTURE.md` if needed.5. **User Approval** -- Presents the requirements for review. The user responds with `APPROVED`, `REJECTED`, or specific change requests.The feature name is sanitized to lowercase with hyphens only (`a-z`, `0-9`, `-`).### Socratic ModeWith `--socratic`, the command uses a structured multi-round discovery process instead of a single question pass. Each round builds on the previous answers to deepen understanding.### Status MarkersThe requirements document progresses through these states:| Status | Meaning ||--------|---------|| DRAFT | Still gathering requirements || REVIEW | Requirements complete, awaiting user approval || APPROVED | User approved, ready for design || REJECTED | Requirements need revision |## Options| Option | Description ||--------|-------------|| `<feature-name>` | **Required.** Name of the feature to plan || `-s`, `--socratic` | Use structured multi-round discovery mode || `--rounds N` | Number of discovery rounds in Socratic mode (default: 3, max: 5) |## Examples```bash# Plan a feature/zerg:plan user-auth# Plan with Socratic discovery/zerg:plan user-auth --socratic# Socratic mode with 5 rounds/zerg:plan payment-api --socratic --rounds 5```## OutputOn completion, the following files are created:```.gsd/ .current-feature # Set to the feature name specs/<feature>/ requirements.md # The requirements document .started # Timestamp of when planning began```## Completion Criteria- `requirements.md` exists with `Status: APPROVED`- All open questions are resolved or accepted- User has explicitly replied with "APPROVED"- Infrastructure needs are identified and documented## See Also- [[zerg-init]] -- Must be run before planning- [[zerg-design]] -- Next step after requirements are approved- [[zerg-Reference]] -- Full command index

Frequently asked questions

Zerg:plan