What is {{project_slug}}-spec?

A specification-maintenance procedure that reads the project's Confluence pages, turns a bug or feature idea into proposed requirements, decisions, and architecture sections, and creates matching Jira tickets. Jira is a system for tracking planned work.

It is for investigating bugs, refining features, recording technical decisions, and preparing linked Confluence and Jira updates after confirmation.

It gives new work a documented place and links the explanation of the change to the tasks that implement it. It adds proposed sections without overwriting approved material.

{{project_slug}}-spec — Skill for Claude Code by big-emotion

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add big-emotion/agent-atelier --skill spec

Clone the repo

git clone --depth 1 https://github.com/big-emotion/agent-atelier

Made for: Claude Code.

Or install project-standard, the plugin that ships this one along with the rest of its 6 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

$agentmods badge for {{project_slug}}-spec$

README.md

[![agentmods](https://agentmods.dev/badge/skills/big-emotion/agent-atelier/spec/github.svg)](https://agentmods.dev/skills/big-emotion/agent-atelier/spec)

Your own site

<a href="https://agentmods.dev/skills/big-emotion/agent-atelier/spec"><img src="https://agentmods.dev/badge/skills/big-emotion/agent-atelier/spec/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

$agentmods 80×15 button for {{project_slug}}-spec$

Your own site · 80×15

<a href="https://agentmods.dev/skills/big-emotion/agent-atelier/spec"><img src="https://agentmods.dev/badge/skills/big-emotion/agent-atelier/spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 5,755 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 92% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.05755
Opus 5.5	$0.00000	$0.02302
Sonnet 5.5	$0.00000	$0.01151
Haiku 4.5	$0.00000	$0.00575

Measured 2mo ago against content hash 622ed56e26b1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

{{project_slug}}-spec scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

92% identical to project-standard-spec — 47 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/project-standard/skills/setup/templates/m3-skills/spec.SKILL.md · 310 lines

How it starts

The opening of the file, as written. The whole thing — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.

{{project_display_name}} Spec

Maintain the {{project_display_name}} spec tree on Confluence. Given a free-text problem (bug, feature, refinement idea), read Confluence (Requirements / Decisions / Architecture) as the canonical source of truth, structure the reflection, propose Pending REQ/DEC/ARCH sections plus matching Jira tickets in {{jira_project_key}}, then — after explicit confirmation — publish Confluence first, Jira second, and close the link loop both ways.

This skill is append-only on Confluence and only writes new sections at status Pending. Humans transition Pending → Implemented → Approved through the Confluence UI. The skill never touches the Status macro of an existing section, never edits the body of a non-Pending section, and never deletes an ID.

When to Activate

User invokes /{{project_slug}}-spec <description> (explicit command).
User writes a natural-language prompt that signals a spec-level reflection:
- bug : … / bug: / "il y a un bug" / "the … is broken"
- j'aimerais ajouter … / "je voudrais ajouter" / "we should add"
- feature idea … / "feature idea" / "what if we"
- comment résoudre … / "comment fixer" / "how do we handle"
- Any free-text describing a problem, gap, or improvement that lacks a Jira ticket and that may touch a REQ/DEC/ARCH.
Do not activate when:
- The user pastes a Jira ticket URL or key — that path belongs to {{project_slug}}-ticket.
- The user asks to flip a Status macro on an existing section (Pending → Implemented, etc.) — that is a Confluence-UI-only operation, refuse and direct them there.
- The user asks to bootstrap or repopulate the spec tree — that is /{{project_slug}}-bootstrap-confluence and runs only once.

If the trigger is ambiguous (the description could be either a pure code question or a spec change), default to activating: the worst case is the user replies with anything other than an affirmative token at Step 6 and nothing is written.

Inputs

Read the full file on GitHub · 310 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 310 lines · 0 tokens per session scan A 622ed56e26b1

Subscribe to this mod's changes

{{project_slug}}-spec is a skill published in the GitHub repository big-emotion/agent-atelier (3 stars, last pushed 24d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,755 tokens. A static security scan graded it A with 0 findings. It is 92% identical to project-standard-spec, differing in 47 lines, and is treated as a copy.

CI and CD Claude Code Documents Project management atlassian claude-code-plugin conventional-commits developer-tooling

{{project_slug}}-spec next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
{{project_slug}}-specbig-emotion/agent-atelier	Skill	3	24d ago	MIT	A	0	Claude Code
skill-doc-deliverynyldn/claude-octopus	Skill	4.4k	today	MIT	A	29	Claude Code
configure-env-variablesmicrosoft/power-platform-skills	Skill	1.1k	yesterday	MIT	A	119	Claude Code
pr-watchSethGammon/Citadel	Skill	927	2d ago	MIT	A	46	Claude Code
sheet-music-publisherbitwize-music-studio/claude-ai-music-skills	Skill	638	3d ago	CC0-1.0	A	36	Claude Code
publishingdanjdewhurst/story-skills	Skill	393	3d ago	MIT	A	204	Claude Code
google-drivesanjay3290/ai-skills	Skill	452	5d ago	Apache-2.0	A	85	Claude Code