agentmods.dev

specs-driven-development-spring-angular specs-artifacts.instructions.md

A set of rules for editing specification files under .specs/, which document the agreed requirements and work plan for a project.

In plain words
What is it for?
Maintaining stable acceptance-criteria and task IDs, recording unresolved questions, preserving ADR filenames, enforcing phase gates, and linking tasks to acceptance criteria and tests.
Why use it?
It prevents accidental invention or renumbering and ensures requirements, questions, tasks, and tests remain traceable and are handled in the correct order.

Instructions file for GitHub Copilot

58 2mo ago A scan 393 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 instructions/loiane/specs-driven-development-spring-angular/specs-artifacts
Clone the repo
git clone --depth 1 https://github.com/loiane/specs-driven-development-spring-angular

Made for: GitHub Copilot.

Per session 393 This file is loaded in full into every session.
When invoked 393 The same file — it is already loaded in full.
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.00393 $0.00393
Opus 5 $0.00197 $0.00197
Sonnet 5 $0.00079 $0.00079
Haiku 4.5 $0.00039 $0.00039

Measured 2d ago against content hash c2104a2a75cd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

specs-driven-development-spring-angular specs-artifacts.instructions.md 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 2d 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.

.github/instructions/specs-artifacts.instructions.md · 34 lines

What it actually says

Spec artifact guardrails

You are editing a file under .specs/. These artifacts ARE the contract between phases — treat them with the same rigor as production code.

Identity rules

  • AC IDs (AC-NNN) and task IDs (T-NNN) are stable. Never renumber. Insertions take the next number, even if it breaks reading order.
  • Q-NNN open questions move from ## Open Questions to ## Resolved Questions with the answer + date — they are not deleted.
  • ADR file names (adr/NNN-<slug>.md) are immutable once committed.

No-invention

If a section requires information you don't have:

  • Add a Q-NNN to ## Open Questions.
  • Halt and ask the user.
  • Do not fill the section with a plausible default.

Phase ordering

You may not edit a higher-numbered artifact (e.g. 04-tasks.md) while a lower-numbered artifact (e.g. 02-spec-review.md) is still in request-changes or has unresolved Q-NNN. The methodology document explains the gates.

Traceability

  • Every task in 04-tasks.md lists AC-IDs and Test-IDs.
  • Every test in src/test/** referenced by a task must use @Tag("AC-NNN") and @DisplayName("AC-NNN: …").
  • 07a-traceability.md enforces zero uncovered ACs and zero orphan tests.

Apply shared/skills/ears-spec-authoring/SKILL.md, shared/skills/spring-task-decomposition/SKILL.md, shared/skills/requirements-traceability/SKILL.md.

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. 2d ago First seen · 34 lines · 393 tokens per session scan A c2104a2a75cd

Subscribe to this mod's changes

specs-driven-development-spring-angular specs-artifacts.instructions.md is an instructions file published in the GitHub repository loiane/specs-driven-development-spring-angular (58 stars, last pushed 2mo ago), licensed MIT. It adds 393 tokens to every session, about $0.0020 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.

DocumentsPlanningTestingangulargithub-copilotjavaspec-driven-developmentspring-boottdd
Related

Other instructions, from other repositories

atmosphere AGENTS.md

Instructions for Atmosphere/atmosphere, covering build system: maven, commands, module build, build only atmosphere-runtime (cpr) and build only spring-boot-starter.

Atmosphere/atmosphere · 7,963 tokens

plugins CLAUDE.md

Instructions for ihub-pub/plugins, covering project knowledge base, project structure, plugin id 速查表, version compatibility and commands（build / lint / test）.

ihub-pub/plugins · 6,974 tokens

featherspec constitution.instructions.md

FeatherSpec constitution editing rules (thin loader).

GregorBiswanger/featherspec · 87 tokens

featherspec knowledge-records.instructions.md

FeatherSpec knowledge record rules — observation, rationale, provenance (thin loader).

GregorBiswanger/featherspec · 99 tokens

featherspec memory-bank.instructions.md

FeatherSpec Memory Bank writing rules (thin loader).

GregorBiswanger/featherspec · 91 tokens

featherspec plans.instructions.md

FeatherSpec plan-file craft rules (thin loader).

GregorBiswanger/featherspec · 89 tokens