spec-driven-development

A Rails-focused workflow for building features with AI agents from systematic plans and self-contained specifications. Spec-driven development means writing the expected behavior down before implementation.

In plain words
What is it for?
It is for planning and implementing Rails features through a structured specification-based process.
Why use it?
It helps turn feature requests into clear specifications, so the agent has defined requirements to follow while building Rails features.

Plugin for Claude Code

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.

Claude Code
/plugin marketplace add maquina-app/rails-claude-code
agentmods
npx agentmods add plugins/maquina-app/rails-claude-code/spec-driven-development
Clone the repo
git clone --depth 1 https://github.com/maquina-app/rails-claude-code

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

spec-driven-development 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.

spec-driven-development/.claude-plugin/plugin.json · 13 lines

What it actually says

{
    "name": "spec-driven-development",
    "version": "1.4.0",
    "description": "A Rails-focused spec-driven development workflow for building features with AI agents through systematic planning and self-contained specs",
    "author": {
        "name": "Mario Alberto Chávez",
        "email": "[email protected]"
    },
    "repository": "https://github.com/maquina-app/rails-claude-code",
    "license": "MIT",
    "keywords": ["rails", "specs", "planning", "workflow", "ai-agents", "sdd"]
}
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 · 13 lines scan A 706b8e915f8a

Subscribe to this mod's changes

spec-driven-development is a plugin published in the GitHub repository maquina-app/rails-claude-code (47 stars, last pushed 17d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.