Skip to content
Agentmart
Submit a tool

specification

Turn a feature, bug, integration, or refactor request into explicit requirements and acceptance criteria before implementation.

Skill by PHENOMVALENCE

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/phenomvalence-specification

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Turn a feature, bug, integration, or refactor request into explicit requirements and acceptance criteria before implementation.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/specification

What's inside

Skill name
specification
Description
Turn a feature, bug, integration, or refactor request into explicit requirements and acceptance criteria before implementation.
License
MIT
Instructions
21 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Specification

## Workflow
1. State the problem and desired user/system outcome.
2. Separate functional requirements from non-functional constraints.
3. Define in-scope and out-of-scope behavior.
4. Identify actors, permissions, data, integrations, and failure modes.
5. Define measurable acceptance criteria.
6. Note compatibility, migration, security, performance, and observability requirements.
7. Record assumptions and unresolved questions.

## Acceptance criteria style
Use observable statements such as:
- Given X, when Y happens, Z is returned/displayed.
- Unauthorized users receive the expected denial.
- Existing behavior A remains unchanged.
- Failure B produces a controlled error and no partial side effect.

Do not begin implementation until the task is specific enough to verify objectively.

From PHENOMVALENCE/engineering-agent-skills, MIT.

More from PHENOMVALENCE/engineering-agent-skills

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Sep 16, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from PHENOMVALENCE

Cite this page

specification skill. Agent Mart. https://agentmart.dev/skills/phenomvalence-specification (last updated 2026-10-24)