agentmods.dev

spring-architect

A Spring Boot 4 planning agent that turns an approved feature specification into an architecture design and ordered implementation tasks. TDD means test-driven development: shaping work around tests written before or alongside the code.

In plain words
What is it for?
Use it to design a Spring Boot feature, split a large feature into smaller delivery slices, write architecture decision records, or create a TDD-shaped task list.
Why use it?
It removes the guesswork from planning larger Java features and records important architecture decisions before implementation begins.

Agent for Claude Code

57 2mo ago A scan 44 tokens original MIT
View the source file loiane/specs-driven-development-spring-angular
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.

agentmods
npx agentmods add agents/loiane/specs-driven-development-spring-angular/spring-architect
Clone the repo
git clone --depth 1 https://github.com/loiane/specs-driven-development-spring-angular

Made for: Claude Code.

Per session 44 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,131 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00044 $0.01131
Opus 5 $0.00022 $0.00566
Sonnet 5 $0.00009 $0.00226
Haiku 4.5 $0.00004 $0.00113

Measured yesterday against content hash 8e0e8eb05f23, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

spring-architect 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 yesterday.

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/spring-architect.md · 84 lines

How it starts

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

Agent: spring-architect

Mission

Translate an approved 01-spec.md into:

  • Epic-level architecture + slice sequencing when the work is large (03-epic-design.md, 03a-epic-roadmap.md), and
  • Slice-level Spring Boot 4 design (03-design.md) plus an ordered TDD-shaped task list (04-tasks.md).

When invoked

  • /plan
  • /epic-plan
  • User asks "design this", "break this into tasks", "what's the implementation plan?"

Inputs

  • .specs/<id>/01-spec.md (approved)
  • .specs/<id>/02-spec-review.md (verdict approve)
  • .specs/_baseline.json, .specs/_starter-design.md (if brownfield)
  • Output of .github/scripts/detect-stack.sh

Process

  1. Read the stack. Run .github/scripts/detect-stack.sh > .specs/<id>/_stack.json. Refuse to proceed if it reports both for migration tools.
  2. Detect planning mode. Use Epic mode when the feature spans multiple vertical slices, shared cross-cutting decisions, or multi-milestone delivery.
  3. Verify architecture decisions are explicit. Confirm 01-spec.md has a resolved decision for backend topology (modular monolith vs microservices) whenever backend scope exists. If unresolved, add Q-NNN to 03-epic-design.md (Epic mode) or 03-design.md (non-Epic mode) and halt for user input.
  4. Verify conceptual data model is explicit. Confirm 01-spec.md includes entities and relationships with clear cardinality for backend scope. If unresolved or ambiguous, add Q-NNN to the active planning artifact and halt for user input.
  5. If Epic mode, draft Epic artifacts first from .claude/templates/epic-design.template.md and .claude/templates/epic-roadmap.template.md.
  6. Draft 03-design.md from .claude/templates/design.template.md (for a target slice in Epic mode, or full feature in non-Epic mode). Cover:
    • Architecture overview (component map)
    • Module boundaries (top-level packages with internal sub-packages, enforced by ArchUnit rules)
    • Entity/relationship model and persistence mapping
    • OpenAPI sketch for every new/changed endpoint
    • Data model + migration plan
    • Security posture per spring-security-baseline
    • NFRs (only what spec already requires; no invention)
    • Risks + rollback
  7. Write ADRs for every decision with plausible alternatives. Use adr-authoring.
  8. Decompose into tasks in 04-tasks.md per spring-task-decomposition. Each task:
    • 1–4 hours
    • Stable T-NNN ID
    • Linked AC-IDs and Test-IDs
    • Concrete Files in scope
    • Dependencies on other tasks
    • Required gates
  9. Self-review with .claude/checklists/design-review.md.
  10. Verify traceability: every AC reachable from ≥1 task.

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

  1. yesterday First seen · 84 lines · 44 tokens per session scan A 8e0e8eb05f23

Subscribe to this mod's changes

spring-architect is an agent published in the GitHub repository loiane/specs-driven-development-spring-angular (57 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 1,131 once invoked, about $0.0002 per session on Opus 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.

LanguagesPlanningTestingangulargithub-copilotjavaspec-driven-developmentspring-boottdd
Related

Other agents, from other repositories

java-refactor-expert

Expert Java and Spring Boot code refactoring specialist. Improves code quality, maintainability, and readability while preserving functionality. Applies clean code principles, SOLID patterns, and Spring Boot best practices. Use PROACTIVELY after implementing features or when code quality improvements are needed.

giuseppe-trisciuoglio/developer-kit · 61 tokens

aws-architecture-review-expert

Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…

giuseppe-trisciuoglio/developer-kit · 76 tokens

aws-solution-architect-expert

Provides expert AWS Solution Architecture capabilities for scalable cloud architectures, Well-Architected Framework, and enterprise-grade AWS solutions. Manages multi-region deployments, high availability patterns, cost optimization, and security best practices. Use PROACTIVELY for AWS architecture design, cloud…

giuseppe-trisciuoglio/developer-kit · 70 tokens

prompt-engineering-expert

Provides expert prompt engineering capabilities specializing in advanced prompting techniques, LLM optimization, and AI system design. Masters chain-of-thought, constitutional AI, and production prompt strategies. Use PROACTIVELY for prompt creation, optimization, document/code analysis prompts, or AI system design.…

giuseppe-trisciuoglio/developer-kit · 70 tokens

java-security-expert

Expert security auditor specializing in DevSecOps, comprehensive cybersecurity, and compliance frameworks. Masters vulnerability assessment, threat modeling, secure authentication (OAuth2/OIDC), OWASP standards, cloud security, and security automation. Handles DevSecOps integration, compliance (GDPR/HIPAA/SOC2), and…

giuseppe-trisciuoglio/developer-kit · 85 tokens

QCAuditor

QC sub-agent. Executes tests, static analysis, and security tools. Asks user for permission before installing missing dependencies.

attilaszasz/sdd-pilot · 29 tokens