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.
npx skills add tranhieutt/software_development_department --skill spec-evolutiongit clone --depth 1 https://github.com/tranhieutt/software_development_departmentWrote 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.
[](https://agentmods.dev/skills/tranhieutt/software_development_department/spec-evolution)<a href="https://agentmods.dev/skills/tranhieutt/software_development_department/spec-evolution"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/spec-evolution/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.
<a href="https://agentmods.dev/skills/tranhieutt/software_development_department/spec-evolution"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/spec-evolution.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00027 | $0.01452 |
| Opus 5 | $0.00014 | $0.00726 |
| Sonnet 5 | $0.00005 | $0.00290 |
| Haiku 4.5 | $0.00003 | $0.00145 |
Grade A, and why
spec-evolution 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Evolution
Purpose
spec-evolution keeps specs alive as the source of truth. When implementation
reality teaches that an approved spec is incomplete, wrong, obsolete, or
conflicting, this workflow resolves the mismatch deliberately before more code is
written.
This is not a shortcut around spec-driven-development. It is the controlled
path for changing a spec after evidence shows the current spec no longer matches
the project.
Core Rule
Do not silently change code to fit reality or silently change the spec to fit code.
Resolve the mismatch explicitly, then continue.
If the mismatch affects behavior, architecture, data, security, release policy, or user-visible workflow, user approval is required before implementation continues.
When To Use
Use this workflow when:
- Tests or implementation reveal the approved spec is impossible or unsafe.
- Code review finds behavior that is useful but not specified.
- Existing code contradicts a new spec.
- A user asks to change requirements after a spec or plan was approved.
- A dependency, API, data model, or platform constraint invalidates the spec.
- A bug fix discovers the desired behavior differs from documented behavior.
Do not use it for:
- Initial spec creation. Use
spec-driven-development. - Pure typo fixes in a spec with no behavior meaning.
- Implementation bugs where the spec is clear and correct. Use
test-driven-developmentordiagnose.
Workflow
1. Freeze Execution
Stop implementation, planning, review approval, or release progression until the mismatch is classified.
State:
Spec evolution gate: execution paused because <spec> and <evidence> disagree.
2. Gather Evidence
Read the minimum required context:
- The approved spec or source-of-truth section
- The code, test, review finding, user request, or runtime evidence that contradicts it
- Any ADR, PRD, API contract, or README section that constrains the decision
- For existing-domain evolution, SHOULD query recent related ledger entries via
/trace-historyto avoid repeating or reversing prior decisions without evidence
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.
- 8d ago First seen · 185 lines · 27 tokens per session scan A cfe600ecc246
spec-evolution is a skill published in the GitHub repository tranhieutt/software_development_department (72 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 1,452 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…
flutter-ui
Build Flutter UI from Figma MCP or image input. Scans src for design tokens (colors, sizes, text styles), existing components, and naming conventions before writing a single line of code. Never hard-codes values.
serena
Serena code intelligence — LSP-powered symbol navigation, diagnostics, and targeted code surgery. Activate before complex refactors, cross-file analysis, or when graph tools need symbol-level depth.
database-migrations
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).
scan
Scan project once per session. Run first — all other skills depend on this.
tdd
Strict test-driven development for behavior changes. Requires verified RED before production code, minimal GREEN, and refactor only after passing tests.