# Create Structured Software Specifications

Unclear feature ideas are hard to turn into reviewable engineering work. This skill guides Claude, Codex, or Claude Code through requirements, design, and task breakdown using EARS notation.

## Install

```bash
npx skillstore add clionegohan/spec
```

## Metadata

- Status: approved
- Slug: clionegohan-spec
- Skillstore revision: r1
- Version status: missing
- Tree hash: 09448b5f01f579e6ca0e76c4cc7c2457ea629532363a36862bb0acee856c7a53
- Author: Clionegohan
- GitHub username: Clionegohan
- License: MIT
- Repository: https://github.com/Clionegohan/YoRuH-Resonance-Archive-C4-Sync-/tree/main/atdd-sdd/.claude/skills/spec
- Ref: 02f077c174c5335e2f5d02ca15e77b70d9543e58
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/clionegohan-spec
- Manifest: https://skillstore.pages.dev/api/skills/clionegohan-spec/manifest

## Capabilities

- Guides a three phase flow for requirements, design, and task breakdown.
- Converts natural language feature requests into user stories.
- Structures acceptance criteria with EARS notation.
- Plans EPIC, Story, and Subtask specification documents.
- Previews generated specification files and related branch or PR prompts.

## Use Cases

- Clarify a New Feature: Turn a rough feature request into user stories and acceptance criteria before implementation begins.
- Plan Engineering Work: Break a large feature into EPIC, Story, and Subtask documents with dependencies and review points.
- Prepare Review Documents: Create a specification package that can support branch creation and a later PR review.

## Prompt Templates

### Start a Basic Spec

```
Create a spec for [feature]. Ask clarifying questions before drafting requirements.
```

### Refine Requirements

```
Turn these rough requirements into user stories and EARS acceptance criteria: [requirements].
```

### Explore Design Options

```
Analyze the existing codebase context for [feature]. Propose design options, tradeoffs, and a task breakdown.
```

### Create a Full Plan

```
Create an EPIC, Story, and Subtask plan for [feature]. Include dependencies, file previews, and branch or PR approval prompts.
```

## Limitations

- It is a planning workflow, not an implementation engine.
- It depends on user approval before moving between phases.
- Branch and PR actions depend on separate \`/branch\` and \`/pr\` skills.
- It does not validate generated files against a project schema.

## Best Practices

- Provide target users, business goals, constraints, and known edge cases.
- Review each phase before asking the assistant to continue.
- Confirm repository side effects before branch or PR workflows run.

## Anti Patterns

- Skipping design exploration when requirements are still unclear.
- Using the skill to implement production code before the specification is approved.
- Ignoring existing architecture when creating tasks and dependencies.

## Security Audit

- Audited at: 2026-07-05T06:30:48.579\+00:00
- Summary: The static analyzer flagged Markdown backticks and inline slash command names as Ruby or shell execution. I found no executable Ruby, shell command execution, prompt injection, network access, or secret access in SKILL.md. The skill documents a specification workflow that asks for confirmation before branch or PR actions.

## Stats

- Views: 169
- Downloads: 10
- Favorites: 0
- Popularity score: 0