Agent skill

Spec Creation

by bybren-llc in bybren-llc/safe-agentic-workflow

Spec creation with pattern references, acceptance criteria, and demo scripts.

MITAuto-check passedProduct & Project Management

Install Spec Creation

skills CLI

$ npx skills add bybren-llc/safe-agentic-workflow --skill spec-creation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install bybren-llc/safe-agentic-workflow spec-creation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/spec-creation .claude/skills/spec-creation && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "spec-creation" agent skill from https://github.com/bybren-llc/safe-agentic-workflow/tree/main/.agents/skills/spec-creation into .claude/skills/spec-creation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-creation", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/bybren-llc/safe-agentic-workflow/tree/main/.agents/skills/spec-creation

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add bybren-llc/safe-agentic-workflow --skill spec-creation -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install bybren-llc/safe-agentic-workflow spec-creation --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflow.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/spec-creation .agents/skills/spec-creation && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "spec-creation" agent skill from https://github.com/bybren-llc/safe-agentic-workflow/tree/main/.agents/skills/spec-creation into .agents/skills/spec-creation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-creation", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add bybren-llc/safe-agentic-workflow --skill spec-creation -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install bybren-llc/safe-agentic-workflow spec-creation --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflow.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/spec-creation .cursor/skills/spec-creation && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "spec-creation" agent skill from https://github.com/bybren-llc/safe-agentic-workflow/tree/main/.agents/skills/spec-creation into .cursor/skills/spec-creation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-creation", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/bybren-llc/safe-agentic-workflow.git --path .agents/skills/spec-creation

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add bybren-llc/safe-agentic-workflow --skill spec-creation -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install bybren-llc/safe-agentic-workflow spec-creation --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflow.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/spec-creation .gemini/skills/spec-creation && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "spec-creation" agent skill from https://github.com/bybren-llc/safe-agentic-workflow/tree/main/.agents/skills/spec-creation into .gemini/skills/spec-creation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-creation", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install bybren-llc/safe-agentic-workflow spec-creation

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add bybren-llc/safe-agentic-workflow --skill spec-creation -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflow.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/spec-creation .github/skills/spec-creation && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "spec-creation" agent skill from https://github.com/bybren-llc/safe-agentic-workflow/tree/main/.agents/skills/spec-creation into .github/skills/spec-creation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-creation", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add bybren-llc/safe-agentic-workflow --skill spec-creation -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install bybren-llc/safe-agentic-workflow spec-creation --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/bybren-llc/safe-agentic-workflow.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/spec-creation .opencode/skills/spec-creation && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "spec-creation" agent skill from https://github.com/bybren-llc/safe-agentic-workflow/tree/main/.agents/skills/spec-creation into .opencode/skills/spec-creation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spec-creation", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: spec-creation
GitHub stars: 423
Token cost: ~1.2k tokens
SKILL.md length: 165 words
Files: 4 (incl. scripts, references, assets)
Skills in repo: 42
Repo updated: Jul 20, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Spec creation with pattern references, acceptance criteria, and demo scripts.

Creating implementation specs
SKILL.md covers Purpose, When This Skill Applies, Stop-the-Line Conditions and Spec Template (MANDATORY), plus 6 more sections
Defining acceptance criteria
Breaking down user stories

What it does

Spec Creation is an agent skill from bybren-llc/safe-agentic-workflow. Spec creation with pattern references, acceptance criteria, and demo scripts. Use when creating implementation specs, defining acceptance criteria, breaking down user stories, or translating business requirements to technical specs. Do NOT use for implementation work -- this is for planning and specification only.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts, reference files and assets.

It sits in Product & Project Management, covering User stories, Translation and PRD writing. The repository describes itself as: SAW — SAFe Agentic Workflow AI Agent Harness for Multi-Agent Team Workflows Built on SAFe methodology (Scaled Agile Framework), adapted for AI agent teams (Now With AI-DLC!)… The licence is MIT.

When your agent uses it

Creating implementation specs
Defining acceptance criteria
Breaking down user stories
Translating business requirements to technical specs

Example prompts

“/spec-creation”

What it can do on your machine

Read from SKILL.md and the folder at commit 26ca58b. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/, which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Spec Creation loads about 1.2k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 165 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~82
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from bybren-llc/safe-agentic-workflow at commit 26ca58b, republished under its MIT licence (© bybren-llc). 165 words, ~1,226 tokens.

Download SKILL.mdSave it as .claude/skills/spec-creation/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.

name: spec-creation
description: Spec creation with pattern references, acceptance criteria, and demo scripts. Use when creating implementation specs, defining acceptance criteria, breaking down user stories, or translating business requirements to technical specs. Do NOT use for implementation work -- this is for planning and specification only.

Spec Creation Skill

TEMPLATE: This skill uses {{PLACEHOLDER}} tokens. Replace with your project values before use.

Purpose

Guide spec creation with clear acceptance criteria, pattern references for execution agents, and testable success validation commands.

When This Skill Applies

Creating implementation specs
Breaking down user stories
Defining acceptance criteria
Adding pattern references for execution
Creating demo scripts for validation
Translating business requirements to technical specs

Stop-the-Line Conditions

FORBIDDEN Patterns

markdown

# FORBIDDEN: Missing acceptance criteria
## Implementation
Just do the thing.

# FORBIDDEN: No pattern reference
## Technical Approach
Build it however you want.

# FORBIDDEN: No success validation
## Done Criteria
Looks good to reviewer.

CORRECT Patterns

markdown

# CORRECT: Clear acceptance criteria
## Acceptance Criteria
- [ ] User can click button -> modal appears
- [ ] Modal shows validation errors for empty fields
- [ ] Successful submission shows success toast

# CORRECT: Pattern reference for execution
## Pattern Reference
- **UI Pattern**: `patterns_library/ui/modal-form.md`
- **API Pattern**: `patterns_library/api/crud-endpoint.md`
- **RLS Pattern**: `patterns_library/security/rls-user-data.md`

# CORRECT: Success validation command
## Success Validation
{{CI_VALIDATE_COMMAND}}

Spec Template (MANDATORY)

Every spec must include:

markdown

# SPEC-{{TICKET_PREFIX}}-{number}: {Feature Name}

## Summary
{One paragraph describing the feature}

## User Story
As a [user type], I want [goal] so that [benefit].

## Acceptance Criteria
- [ ] {Testable criterion 1}
- [ ] {Testable criterion 2}
- [ ] {Testable criterion 3}

## Pattern References
- **UI**: `patterns_library/ui/{pattern}.md`
- **API**: `patterns_library/api/{pattern}.md`
- **Database**: `patterns_library/database/{pattern}.md`
- **Security**: Follow RLS patterns in `docs/database/RLS_IMPLEMENTATION_GUIDE.md`

## Success Validation Command
{validation command}

## Demo Script
1. Navigate to {page}
2. Click {button}
3. Observe {expected behavior}
4. Verify {success indicator}

## Logical Commits
1. `feat(scope): implement data model [{{TICKET_PREFIX}}-{number}]`
2. `feat(scope): add API endpoint [{{TICKET_PREFIX}}-{number}]`
3. `feat(scope): create UI component [{{TICKET_PREFIX}}-{number}]`
4. `test(scope): add unit tests [{{TICKET_PREFIX}}-{number}]`

Acceptance Criteria Patterns

User Action Criteria

markdown

- [ ] User can {action} -> {result}
- [ ] When user {triggers}, system {responds}
- [ ] User receives {feedback} after {action}

Data Criteria

markdown

- [ ] Data persists after {action}
- [ ] User can only see their own {data type}
- [ ] {field} validates {constraint}

Error Criteria

markdown

- [ ] Invalid input shows {error message}
- [ ] Network failure shows retry option
- [ ] Unauthorized access returns 401

Pattern Discovery for Specs

Before writing any spec:

bash

# Find existing patterns
ls patterns_library/

# Search for similar implementations
grep -r "similar feature" app/ lib/

# Check existing specs for format
ls specs/

Spec Quality Checklist

Before submitting spec:

All acceptance criteria are testable (can verify pass/fail)
Pattern references point to existing patterns
Success validation command is runnable
Demo script is step-by-step reproducible
Logical commits follow SAFe format
Ticket referenced

Output Locations

Output Type	Location
Impl specs	`specs/SPEC-{{TICKET_PREFIX}}-{number}-{description}.md`
Requirements	`docs/agent-outputs/requirements/{{TICKET_PREFIX}}-*.md`
ADRs	`docs/adr/ADR-{number}-{description}.md`

Evidence for Ticket System

After spec approval:

markdown

**BSA Spec Evidence**

**Spec**: specs/SPEC-{{TICKET_PREFIX}}-{number}-{description}.md
**Status**: Approved by [reviewer]

**Deliverables**:
- [x] Acceptance criteria defined
- [x] Pattern references added
- [x] Demo script created
- [x] Ready for implementation

Authoritative References

Spec Template: docs/archive/specs/spec_template.md
Pattern Library: patterns_library/README.md
Planning Guide: docs/team/PLANNING-AGENT-META-PROMPT.md
SAFe Workflow: CONTRIBUTING.md

Files

SKILL.md and 3 other files (scripts, references, assets) in .agents/skills/spec-creation of bybren-llc/safe-agentic-workflow.

SKILL.md
assets/.gitkeep
references/.gitkeep
scripts/.gitkeep

Open the folder on GitHubat commit 26ca58b

Compare with similar skills

Spec Creation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Spec Creation compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Spec Creation this skillbybren-llc/safe-agentic-workflow	423	—	~1.2k	Automated safety check: Pass	MIT	2 mo ago
Ralph Tui Create Beadssubsy/ralph-tui	2.5k	1 repos	~2.6k	Automated safety check: Pass	MIT	1 mo ago
Ralph Tui Create Beads Rustsubsy/ralph-tui	2.5k	1 repos	~2.8k	Automated safety check: Pass	MIT	1 mo ago
Ralph Tui Create JSONsubsy/ralph-tui	2.5k	1 repos	~2.6k	Automated safety check: Pass	MIT	1 mo ago
To Prdywwynm/EverythingDone	144	11 repos	~777	Automated safety check: Pass	GPL-3.0	yesterday
Use Case Writerphucnt-bazone-vietnam/use-case-writer	142	—	~4.1k	Automated safety check: Pass	MIT	4 mo ago

Similar skills

Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
2.5k GitHub starsUsed in 1 repo~2.6k tokens
Product & Project ManagementAuto-check passed
Ralph Tui Create Beads Rust
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).
2.5k GitHub starsUsed in 1 repo~2.8k tokens
Product & Project ManagementAuto-check passed
Ralph Tui Create JSON
subsy/ralph-tui
Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.
2.5k GitHub starsUsed in 1 repo~2.6k tokens
Product & Project ManagementAuto-check passed
To Prd
ywwynm/EverythingDone
Turn the current conversation context into a PRD and publish it to the project issue tracker.
144 GitHub starsUsed in 11 repos~777 tokens
Product & Project ManagementAuto-check passed
Use Case Writer
phucnt-bazone-vietnam/use-case-writer
Generate Use Case specifications in English Markdown following the IT BA standard 13-field template (Karl Wiegers / IIBA).
142 GitHub stars~4.1k tokensUpdated 4 mo ago
Product & Project ManagementAuto-check passed
Project Planner
adrianpuiu/claude-skills-marketplace
Comprehensive project planning and documentation generator for software projects.
100 GitHub starsUsed in 1 repo~6k tokens
Product & Project ManagementAuto-check passed

Questions about Spec Creation

What does Spec Creation do?

Spec creation with pattern references, acceptance criteria, and demo scripts. Spec Creation is an agent skill from bybren-llc/safe-agentic-workflow. Spec creation with pattern references, acceptance criteria, and demo scripts.

When should I use Spec Creation?

Spec Creation fits situations like: creating implementation specs; defining acceptance criteria; breaking down user stories; translating business requirements to technical specs.

How do I install Spec Creation in Claude Code?

Run `npx skills add bybren-llc/safe-agentic-workflow --skill spec-creation -a claude-code`. Or copy the skill folder (.agents/skills/spec-creation in bybren-llc/safe-agentic-workflow) into .claude/skills/spec-creation in your project. Claude Code loads it when a task matches its description.

How do I install Spec Creation in Codex?

Run `npx skills add bybren-llc/safe-agentic-workflow --skill spec-creation -a codex`. Or copy the skill folder (.agents/skills/spec-creation in bybren-llc/safe-agentic-workflow) into .agents/skills/spec-creation in your project. Codex loads it when a task matches its description.

Can I use Spec Creation in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bybren-llc/safe-agentic-workflow --skill spec-creation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/spec-creation, .gemini/skills/spec-creation, .github/skills/spec-creation and .opencode/skills/spec-creation in your project.

What does Spec Creation need to run?

SKILL.md names no scripts, command-line tools or credentials: Spec Creation is instructions for the agent only.

Does Spec Creation access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Spec Creation safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Spec Creation use?

Spec Creation is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Spec Creation use?

About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Spec Creation?

Skills that share tags, products or a category with Spec Creation: Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars), Ralph Tui Create JSON (subsy/ralph-tui, 2.5k stars) and To Prd (ywwynm/EverythingDone, 144 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Spec Creation?

bybren-llc (a GitHub organization) maintains it in bybren-llc/safe-agentic-workflow, which has 423 GitHub stars. The repository holds 42 skills in this directory. The repository was last updated on July 20, 2026.

Source: bybren-llc/safe-agentic-workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Spec Creation

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Spec Creation Skill

Purpose

When This Skill Applies

Stop-the-Line Conditions

FORBIDDEN Patterns

CORRECT Patterns

Spec Template (MANDATORY)

Acceptance Criteria Patterns

User Action Criteria

Data Criteria

Error Criteria

Pattern Discovery for Specs

Spec Quality Checklist

Output Locations

Evidence for Ticket System

Authoritative References

Files

Compare with similar skills

Similar skills

More from bybren-llc/safe-agentic-workflow

Related

Questions about Spec Creation