specwright-spec-authoring

Author specwright-compatible specs with complete frontmatter, bounded scope, deterministic test plans, and acceptance criteria that map directly to…

Skill by benthepsychologist

IndexedApache-2.0★ 3

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/benthepsychologist-specwright-spec-authoring

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.

About

Author specwright-compatible specs with complete frontmatter, bounded scope, deterministic test plans, and acceptance criteria that map directly to deliverables.

Use cases: testing

Reviews

Write a review

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/specwright-spec-authoring

Tools it pre-approves 2

From allowed-tools in SKILL.md: the agent may use these without asking you each time.

bash
rg

What's inside

Skill name: specwright-spec-authoring
Description: Author specwright-compatible specs with complete frontmatter, bounded scope, deterministic test plans, and acceptance criteria that map directly to deliverables.
License: Apache-2.0
Allowed tools: bash, rg
Metadata: author: benthepsychologist · version: 1.0
Instructions: 56 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

# Specwright Spec Authoring

Use this skill when creating or revising a spec consumed by the Specwright execution flow.

## Required frontmatter

Every spec starts with fully populated YAML frontmatter:

```yaml
---
id: t000-00-example
tier: B
title: "Outcome-focused title"
owner: your-handle
goal: Clear one-sentence objective
validated: true
version: "2.0"
labels:
  - specwright
epic: t000-epic
repo:
  name: project-name
  url: /workspace/project
  working_branch: feat/example
depends_on: []
created: "2026-03-20T00:00:00Z"
updated: "2026-03-20T00:00:00Z"
---
```

## Body structure

Include these sections in order:

1. Objective
2. Problem
3. Deliverables
4. Test Plan
5. Acceptance Criteria
6. Boundary

## Writing rules

- Use explicit paths, commands, and artifacts.
- Avoid ambiguous terms like "handle", "improve", or "cleanup" without measurable criteria.
- Keep in-scope and out-of-scope clearly separated.

## Quick structural check

```bash
rg -n "^## (Objective|Problem|Deliverables|Test Plan|Acceptance Criteria|Boundary)" <spec-file>.md
```

If any required section is missing, revise before handoff.

From benthepsychologist/specwright, Apache-2.0.

Signals

Stars: 3
Forks: 0
Open issues: 1
Last commit (this folder): Mar 20, 2026 (7 months ago)
Last release: Nov 10, 2025 (11 months ago)

From GitHub (fetched Oct 24, 2026).

Details

Version: 1.0
License: Apache-2.0
Repository: github.com/benthepsychologist/specwright
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from benthepsychologist

Cite this page

specwright-spec-authoring skill. Agent Mart. https://agentmart.dev/skills/benthepsychologist-specwright-spec-authoring (last updated 2026-10-24)