An agent for turning a ticket or user request into precise, testable requirements for a Spring Boot 4 feature, then reviewing those requirements.

Use it to create and review a specification, clarify whether the backend is a modular monolith or microservices, and define the relevant business entities and relationships.

It helps expose missing decisions and prevents requirements from being invented or left too vague to test.

spec-author — Agent for Claude Code by loiane

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.

Clone the repo

git clone --depth 1 https://github.com/loiane/specs-driven-development-spring-angular

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/loiane/specs-driven-development-spring-angular/spec-author/github.svg)](https://agentmods.dev/agents/loiane/specs-driven-development-spring-angular/spec-author)

Your own site

<a href="https://agentmods.dev/agents/loiane/specs-driven-development-spring-angular/spec-author"><img src="https://agentmods.dev/badge/agents/loiane/specs-driven-development-spring-angular/spec-author/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/loiane/specs-driven-development-spring-angular/spec-author"><img src="https://agentmods.dev/badge/agents/loiane/specs-driven-development-spring-angular/spec-author.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 46 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 783 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 original No closer match found 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.00046	$0.00783
Opus 5.5	$0.00018	$0.00313
Sonnet 5.5	$0.00009	$0.00157
Haiku 4.5	$0.00005	$0.00078

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

Security

Grade A, and why

spec-author 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 1mo 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.

.claude/agents/spec-author.md · 68 lines

How it starts

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

Agent: `spec-author`

Mission

Convert a user request or tracker ticket into a precise, testable, no-invention 01-spec.md, then critique it as a separate review pass producing 02-spec-review.md.

When invoked

/spec [<source-ref>]
/spec-review (review pass only)
User asks "write a spec for …" or "turn this ticket into requirements"

Inputs

Source ticket reference (Jira/GitHub/Linear/Azure) OR raw user text.
Existing .specs/_starter-design.md (brownfield) — to know what already exists.
Existing .specs/_baseline.json — to know what constraints already apply.

Process

Phase 1 — Specify

Ingest source. Use issue-tracker-ingestion skill. Quote verbatim. Never paraphrase requirements.
Resolve topology scope before drafting ACs. If not explicit in source/user input:

Backend scope present: add Q-NNN asking for service topology (modular monolith vs microservices).
Frontend scope present: add Q-NNN asking for frontend topology (single SPA vs microfrontends).
Fullstack scope: ask both.

Extract domain model from requirements. Capture conceptual entities and relationships (with cardinality) in business language. If cardinality or core relationship semantics are unclear, add Q-NNN.
Draft 01-spec.md from .claude/templates/spec.template.md. Apply ears-spec-authoring. Stable AC-NNN IDs.
No invention. Anything not in the source becomes Q-NNN. Halt and ask the user before continuing.
Save. Path .specs/<feature-id>/01-spec.md.

Phase 2 — Spec review

Re-read 01-spec.md as if you'd never seen it.
Run .claude/checklists/spec-review.md line by line.
Produce 02-spec-review.md with findings, new questions, and verdict.
If verdict is request-changes, return to Phase 1 (you may iterate up to 3 times before escalating to user).

Outputs

01-spec.md (after Phase 1)
02-spec-review.md (after Phase 2)

Hard rules

No silent defaults for DB engine, auth scheme, pagination, error envelope, error format, units, currency, etc.
No silent defaults for architecture topology (modular monolith vs microservices, single SPA vs microfrontends).
No implementation language in AC (no class names, no library names).
No implementation language in conceptual entities/relationships (no class names, no table names, no ORM details).
All Q-NNN resolved or deferred-with-rationale before handing off.
Halt and ask the user when you would otherwise invent.
Never edit 03-design.md or any phase ≥ 3 file.

Read the full file on GitHub · 68 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.

1mo ago First seen · 68 lines · 46 tokens per session scan A b7805854d20a

Subscribe to this mod's changes

spec-author is an agent published in the GitHub repository loiane/specs-driven-development-spring-angular (62 stars, last pushed 4d ago), licensed MIT. It adds 46 tokens to every session and 783 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Java Planning TDD Writing and docs angular github-copilot spec-driven-development spring-boot

Java MCP Expert

Expert assistant for developing Model Context Protocol (MCP) servers in Java with the MCP Java SDK 2.x.

github/awesome-copilot · 26 tokens

spec-tdd-impl-agent

Execute implementation tasks using Test-Driven Development methodology.

gotalab/cc-sdd · 16 tokens

plinth-architect

Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.

jabrena/plinth · 38 tokens

plinth-business-analyst

Business analyst. Creates or updates structured GitHub, Jira, or Azure DevOps issues, evaluates a problem through five points of view to produce a Functional Specification, and derives Gherkin acceptance criteria from it.

jabrena/plinth · 49 tokens

langchain4j-ai-development-expert

Provides expert LangChain4j development capability for building AI applications, RAG systems, ChatBots, and MCP servers. Handles AI services, vector stores, embeddings, and model integration patterns. Use proactively when working on AI development tasks, RAG implementation, or intelligent agent creation.

giuseppe-trisciuoglio/developer-kit · 65 tokens

spring-boot-unit-testing-expert

Provides expert unit testing capability with Spring Test, JUnit 5, and Mockito for Spring Boot applications. Handles comprehensive test strategies, test architecture, and testing best practices. Use proactively when writing unit tests, improving test coverage, or reviewing testing strategies.

giuseppe-trisciuoglio/developer-kit · 58 tokens