New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Ad Spec

by CorridorTech in CorridorTech/PoseCap

Draft a feature-level specification at doc/specs/NNNN-<slug.md following the kit's six-layer artifact stack (Constitution → Domain → Product → Spec → Plan/Decisions → Code).

Apache-2.0Auto-check: notesProduct & Project Management

Install Ad Spec

skills CLI
$ npx skills add CorridorTech/PoseCap --skill ad-spec -a claude-code

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

GitHub CLI
$ gh skill install CorridorTech/PoseCap ad-spec --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/CorridorTech/PoseCap.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/ad-spec .claude/skills/ad-spec && 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/

Facts

Skill name
ad-spec
GitHub stars
224
Token cost
~2.2k tokens
SKILL.md length
906 words
Files
1
Skills in repo
15
Repo updated
First seen
Licence
Apache-2.0

At a glance

Draft a feature-level specification at doc/specs/NNNN-<slug.md following the kit's six-layer artifact stack (Constitution → Domain → Product → Spec → Plan/Decisions → Code).

  • Works in 5 steps: Determine NNNN and slug → Confirm scope → Interview to fill → …
  • The user wants to write
  • SKILL.md covers Step 1 — Determine NNNN and slug, Step 2 — Confirm scope, Step 3 — Interview to fill and Interview UX, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Ad Spec is an agent skill from CorridorTech/PoseCap. Draft a feature-level specification at doc/specs/NNNN-<slug.md following the kit's six-layer artifact stack (Constitution → Domain → Product → Spec → Plan/Decisions → Code). Adapts GitHub Spec Kit's mandatory sections (User Scenarios, Requirements, Success Criteria) to the kit's documentation discipline. Use when the user wants to write, draft, scaffold, or open a feature spec, feature brief, user stories, or success criteria for one feature multiple tasks will implement. Product-level scoping (PRD, multi-feature…

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering PRD writing and Product metrics. It works with GitHub. The licence is Apache-2.0.

When your agent uses it

  • The user wants to write
  • Open a feature spec
  • Success criteria for one feature multiple tasks will implement

Example prompts

  • “/ad-spec”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Glob, Bash

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Determine NNNN and slug
  2. Confirm scope
  3. Interview to fill
  4. Write the file
  5. Editing guidance for later turns

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Glob
    • Bash

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    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

Ad Spec loads about 2.2k tokens when it runs. Until then it costs about 193 tokens; SKILL.md has 906 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~193
When it runs · the whole SKILL.md, loaded when a task matches
~2.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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Write, Glob, Bash

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from CorridorTech/PoseCap at commit 626701b, republished under its Apache-2.0 licence (© CorridorTech). 906 words, ~2,224 tokens.

Download SKILL.mdSave it as .claude/skills/ad-spec/SKILL.md (or your agent's skills folder).
name
ad-spec
description
Draft a feature-level specification at doc/specs/NNNN-<slug>.md following the kit's six-layer artifact stack (Constitution → Domain → Product → Spec → Plan/Decisions → Code). Adapts GitHub Spec Kit's mandatory sections (User Scenarios, Requirements, Success Criteria) to the kit's documentation discipline. Use when the user wants to write, draft, scaffold, or open a feature spec, feature brief, user stories, or success criteria for one feature multiple tasks will implement. Product-level scoping (PRD, multi-feature roadmap, target user, product success metrics) belongs to `ad-prd` (Layer 3); this skill is feature-level only. Status starts at draft; the file is the binding feature contract once accepted; references parent PRD for product-scope inheritance.
allowed-tools
Read, Write, Glob, Bash
summary
Draft a feature spec at `doc/specs/NNNN-<slug>.md` (Spec Kit-aligned mandatory sections). Layer 4 of the six-layer artifact stack. References parent PRD…

/ad-spec

Drafts doc/specs/<NNNN>-<short-slug>.md for one feature. Status lifecycle: draft → accepted → shipped | superseded by SPEC-NNNN. Spec is the layer-4 artifact in the kit's six-layer stack — Constitution (AGENTS.md + WORKFLOW.md) → Domain (CONTEXT.md) → Product (doc/product/PRD.md) → Spec (this skill) → Plan/Decisions (ARCHITECTURE.md + doc/adr/ + doc/tasks/) → Code. Multiple tasks implement one spec; ADRs may be driven by spec constraints. The Domain layer (CONTEXT.md, ubiquitous language per Evans 2003) is the source of canonical nouns the spec must use; if the spec introduces a new noun, resolve it through CONTEXT.md first. The Product layer (PRD.md) is the source of target user, product-level success metrics, and cross-feature constraints the spec inherits from; a feature spec whose target user or success metric contradicts the PRD is drift that ad-drift flags.

Step 1 — Determine NNNN and slug

List doc/specs/. NNNN = next available 4-digit number after the highest existing (mirrors the ADR and task conventions). If doc/specs/ does not exist, create it; start at 0001. Slug: kebab-case, ≤6 words, derived from the feature title.

Step 2 — Confirm scope

The spec captures one feature. If the user's request implies multiple features, ask which one to write first; the others become follow-up specs. A "feature" here is the smallest user-visible outcome that has its own success criteria — not a task (work unit) and not a binding architectural decision (ADR).

Step 3 — Interview to fill

Ask one question per missing field, in this order. Skip the philosophical questions and the questions whose answers are already obvious from the conversation.

  • Context: business context first. Why the feature exists, the user / constraint / problem it addresses, the cost of not building it.
  • User Scenarios: Given-When-Then for the key flows. Each scenario must be independently testable. Multiple scenarios when the feature has more than one path.
  • Functional Requirements: testable statements. Plain bullets (no checkbox — Spec is decision-record, not tracking; implementation tracking lives in per-Spec tasks). "User can sign in with email and password" — yes. "Authentication should be secure" — no, that's not a requirement, it's a hope.
  • Non-functional Requirements: performance, security, accessibility, observability — only the constraints that bind. Plain bullets. Skip when there are none.
  • Success Criteria: measurable per WORKFLOW.md §1. Plain bullets — pass/fail must be observable, not aspirational. "Loads in under 2 seconds at p95 over 7 days" — yes. "Loads fast" — no. Per-criterion progress tracking lives in tasks; the Spec carries the criteria definitions and a single Status: field per ADR-0030 §1.
  • Edge Cases: empty inputs, large inputs, concurrent access, missing prerequisites, permission errors. Surface them before code is written, not after a bug report.
  • Out of Scope: explicit non-goals. Anything readers might assume is in scope but isn't. Prevents scope creep without an audit trail.
  • Open Questions: deferred decisions. Each becomes a follow-up ADR or an explicit punt with a rationale.
  • Related: ADRs touched by this spec, tasks implementing it (filled lazily as tasks are created), other specs this one supersedes or depends on.

Status starts at draft. Created: today, ISO format. Owner: ask. Do not invent values — when the user does not know, leave <TODO> and ask.

Interview UX

When the host exposes AskUserQuestion, use it for multi-choice prompts (Status: draft / accepted / shipped, owner selection from team members, scope-vs-multiple-features confirmation) and for confirmation gates with non-trivial branching. Inline text questions are an acceptable fallback only when the host lacks a structured-prompt primitive (Codex). One question per gate; do not chain three text questions when one AskUserQuestion card lists the options.

Show full SKILL.md (344 more words)Show less

Step 4 — Write the file

Path: doc/specs/<NNNN>-<short-slug>.md. Use the template below.

Stop after writing. Do not flip status to accepted — that requires user review.

Step 5 — Editing guidance for later turns

When the user later works on the spec, edit the file by:

  • Appending to Open Questions (close them with the resolution; never delete them).
  • Flipping Status to accepted once the user signs off and tasks start being created.
  • Flipping Status to shipped after release — once all per-Spec tasks complete.
  • Flipping Status to superseded by SPEC-NNNN when a later spec replaces this one.
  • Adding Tasks entries to Related as tasks are created against this spec.

Implementation tracking (per-criterion progress) lives in the per-Spec tasks, not in the Spec itself. The Spec is the contract; tasks track its construction.

Never rewrite existing prose — append rationale to Open Questions as a resolution paragraph rather than mutating the original requirement text.

Template — doc/specs/NNNN-<slug>.md

markdown
# Spec `<NNNN>`: `<short imperative title>`

**Status:** `<draft | accepted | shipped | superseded by SPEC-NNNN>`
**Created:** `<YYYY-MM-DD>`
**Owner:** `<name or role>`

## Context

`<Why this feature exists. The user, the constraint, the problem. What would break if this feature did not ship.>`

## User Scenarios

`<Given-When-Then for the key flows. Each scenario independently testable.>`

- **Scenario 1:** `<short title>`
  - Given `<starting state>`
  - When `<action>`
  - Then `<observable outcome>`

## Requirements

### Functional

- `<R1: testable statement>`
- `<R2>`

### Non-functional

- `<perf / security / a11y / observability — only when binding>`

## Success Criteria

Definitional. Measurable conditions; pass/fail observable, not aspirational. Per-criterion progress tracking lives in per-Spec tasks, not here.

- `<criterion 1: measurable, observable>`
- `<criterion 2>`

## Edge Cases

- `<empty input behavior>`
- `<large input / failure modes>`
- `<permission / concurrency / state-restoration cases>`

## Out of Scope

`<Explicit non-goals. Anything readers might assume is in scope but isn't.>`

## Open Questions

`<Deferred decisions. Each becomes an ADR or a documented punt.>`

## Related

- ADRs: `<list with links — written as the spec is accepted>`
- Tasks: `<doc/tasks/NNNN-... — appended as tasks are created>`
- Supersedes / Depends on: `<other spec links if any>`

Output contract

A single new file at doc/specs/<NNNN>-<short-slug>.md. Status draft. Tasks list empty (filled lazily as tasks land). No existing specs modified. No invented values.

The spec is a narrative document but is exempt from ADR-0008's no-dates rule for the same reason ADRs and tasks are: the Status lifecycle and Created field are part of the auditability primitive. The remaining documentation discipline rules apply at write time:

  • No emoji anywhere in the file.
  • Context is the business-context-first section — why the feature exists before what it does.
  • One scope: one feature per spec. Multiple features implies multiple specs.
  • No speculation. Open Questions go in their named section; everywhere else captures decisions.
  • No commented-out requirements or TODO/FIXME — every deferred item references a tracked work item or lives under Open Questions.

Next

  • /ad-ground for the four-source research pass before code (WORKFLOW §4 + §5).
  • /ad-task to break the spec into work units; each task carries a Spec ref field pointing back to this file.
  • /ad-adr if scoping the spec surfaced a binding architectural decision worth recording (one decision per ADR).
  • Flip Status to accepted once you sign off and tasks start being created. Flip to shipped after release.

© CorridorTech, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/ad-spec of CorridorTech/PoseCap.

Open the folder on GitHubat commit 626701b

Compare with similar skills

Ad Spec 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.

Ad Spec compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ad Spec this skillCorridorTech/PoseCap224—~2.2kAutomated safety check: NotesApache-2.0
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Ouroboros PM InterviewQ00/ouroboros6.2k1 repos~5.7kAutomated safety check: PassMIT
To Issuessmallnest/pigo475—~1.9kAutomated safety check: PassMIT
Write A Prdbestofjs/bestofjs3.1k1 repos~722Automated safety check: PassMIT
Write Update Tidb Docspingcap/docs616—~2.3kAutomated safety check: PassCustom licence

Similar skills

  • CCPM Project Management

    automazeio/ccpm

    Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

  • Ouroboros PM Interview

    Q00/ouroboros

    Runs a guided product-manager interview that classifies each question automatically and produces a Product Requirements Document.

    6.2k GitHub starsUsed in 1 repo~5.7k tokens
    Product & Project ManagementAuto-check passed

  • To Issues

    smallnest/pigo

    Decompose a PRD and/or SPEC into implementable Issues and create them in your chosen platform (GitHub, Local, or Baidu iCafe).

    475 GitHub stars~1.9k tokensUpdated 25 days ago
    Product & Project ManagementAuto-check passed

  • Write A Prd

    bestofjs/bestofjs

    Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue.

    3.1k GitHub starsUsed in 1 repo~722 tokens
    Product & Project ManagementAuto-check passed

  • Write Update Tidb Docs

    pingcap/docs

    Write new TiDB documentation or update existing TiDB documentation from code changes, PRs, issues, design docs, product specs, rough drafts, existing docs, or short feature descriptions.

    616 GitHub stars~2.3k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

  • Prd

    juanandresgs/claude-ctrl

    Write structured feature specifications with problem statements, user journeys, use cases, functional requirements, and success metrics.

    193 GitHub stars~2.9k tokensUpdated 2 mo ago
    Product & Project ManagementAuto-check passed

More from CorridorTech/PoseCap

All 15 skills in this repo

  • Ad Adr

    CorridorTech/PoseCap

    Draft a new ADR (Architecture Decision Record) at doc/adr/NNNN-<short-title.md, using Michael Nygard's Context/Decision/Consequences/Alternatives pattern.

    224 GitHub stars~1k tokensUpdated yesterday
    Auto-check: notes

  • Ad Architecture

    CorridorTech/PoseCap

    Generate ARCHITECTURE.md at the repo root by scanning the code first, pre-filling layers/patterns/observability/deployment from observed signals, then asking only the genuine gaps.

    224 GitHub stars~1.5k tokensUpdated yesterday
    Auto-check: notes

  • Ad Archive

    CorridorTech/PoseCap

    Hard-delete completed plan files (tasks Status:done, specs Status:shipped, PRDs Status:superseded, ADRs Status:superseded or deprecated) via git rm, leaving git history as the only ledger.

    224 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check: notes

  • Ad Drift

    CorridorTech/PoseCap

    Read-only drift audit — compare AGENTS.md, ARCHITECTURE.md, ADR statuses, feature specs in doc/specs/, and documentation discipline against what the code actually does.

    224 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check: notes

  • Ad Hooks

    CorridorTech/PoseCap

    Scaffold deterministic quality gates per WORKFLOW.md §11 — pre-commit (lint, format, secret-scan), pre-push (build, unit, integration).

    224 GitHub stars~2.4k tokensUpdated yesterday
    Auto-check: notes

  • Ad Next

    CorridorTech/PoseCap

    Survey the project's state across the six-layer artifact stack and recommend prioritized next actions, modeled on flutter doctor.

    224 GitHub stars~3.3k tokensUpdated yesterday
    Auto-check: notes

Works with

Categories

Questions about Ad Spec

What does Ad Spec do?

Draft a feature-level specification at doc/specs/NNNN-<slug.md following the kit's six-layer artifact stack (Constitution → Domain → Product → Spec → Plan/Decisions → Code). Ad Spec is an agent skill from CorridorTech/PoseCap.md following the kit's six-layer artifact stack (Constitution → Domain → Product → Spec → Plan/Decisions → Code).

When should I use Ad Spec?

Ad Spec fits situations like: the user wants to write; open a feature spec; success criteria for one feature multiple tasks will implement.

How do I install Ad Spec in Claude Code?

Run `npx skills add CorridorTech/PoseCap --skill ad-spec -a claude-code`. Or copy the skill folder (.claude/skills/ad-spec in CorridorTech/PoseCap) into .claude/skills/ad-spec in your project. Claude Code loads it when a task matches its description.

How do I install Ad Spec in Codex?

Run `npx skills add CorridorTech/PoseCap --skill ad-spec -a codex`. Or copy the skill folder (.claude/skills/ad-spec in CorridorTech/PoseCap) into .agents/skills/ad-spec in your project. Codex loads it when a task matches its description.

Can I use Ad Spec 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 CorridorTech/PoseCap --skill ad-spec -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ad-spec, .gemini/skills/ad-spec, .github/skills/ad-spec and .opencode/skills/ad-spec in your project.

What does Ad Spec need to run?

SKILL.md names no scripts, command-line tools or credentials: Ad Spec is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Glob, Bash.

Does Ad Spec 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 Ad Spec safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Ad Spec use?

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

How many tokens does Ad Spec use?

About 2.2k tokens (SKILL.md is roughly 8.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 Ad Spec?

Skills that share tags, products or a category with Ad Spec: CCPM Project Management (automazeio/ccpm, 8.4k stars), Ouroboros PM Interview (Q00/ouroboros, 6.2k stars), To Issues (smallnest/pigo, 475 stars) and Write A Prd (bestofjs/bestofjs, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ad Spec?

CorridorTech (a GitHub organization) maintains it in CorridorTech/PoseCap, which has 224 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 7, 2026.

Source: CorridorTech/PoseCap on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.