What is fullstack-dev-kit?

A workflow for taking a software issue from a tracker to a pull request, the proposed code change submitted for review. It can use stories from Jira, Linear, GitHub Issues, or Azure DevOps, and linked Figma designs.

Use it to implement user stories, create end-to-end tests, check coverage and security, open a pull request, fix review findings, and move the issue to review.

It brings planning, implementation, testing, security checks, review fixes, and ticket updates into one process. This reduces the manual coordination needed to turn a request into a reviewed change.

fullstack-dev-kit — Plugin for Claude Code by theam/claude-dev-kit

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/theam/claude-dev-kit

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/plugins/theam/claude-dev-kit/claude-dev-kit/github.svg)](https://agentmods.dev/plugins/theam/claude-dev-kit/claude-dev-kit)

Your own site

<a href="https://agentmods.dev/plugins/theam/claude-dev-kit/claude-dev-kit"><img src="https://agentmods.dev/badge/plugins/theam/claude-dev-kit/claude-dev-kit/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/plugins/theam/claude-dev-kit/claude-dev-kit"><img src="https://agentmods.dev/badge/plugins/theam/claude-dev-kit/claude-dev-kit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session not measured What this adds to a session before it is invoked.

When invoked not measured The manifest loads nothing itself; its 1 skill, 5 commands, 9 agents, 3 hooks, 3 MCP servers, 1 plugin cost 820 tokens a session between them.

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.

Security

Grade A, and why

fullstack-dev-kit 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 17d 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-plugin/plugin.json · 34 lines

What it actually says

{
  "name": "fullstack-dev-kit",
  "version": "0.19.18",
  "description": "Issue-to-PR workflow kit for any tech stack. Fetch a user story from your tracker (Jira, Linear, GitHub Issues, Azure DevOps) and any linked Figma designs, implement with plan approval, enforce >95% coverage and a security pass, generate e2e tests, open the PR, fix review findings, and move the ticket to review.",
  "license": "Apache-2.0",
  "homepage": "https://github.com/theam/claude-dev-kit",
  "repository": "https://github.com/theam/claude-dev-kit",
  "author": {
    "name": "The Agile Monkeys",
    "email": "[email protected]"
  },
  "keywords": [
    "workflow",
    "jira",
    "linear",
    "github-issues",
    "azure-devops",
    "figma",
    "coverage",
    "code-review",
    "pull-request",
    "tech-stack-agnostic"
  ],
  "userConfig": {
    "telemetry_enabled": {
      "type": "boolean",
      "title": "Share anonymous usage telemetry (fallback toggle)",
      "description": "OFF by default. Consent is normally set by the `npm create @theagilemonkeys/dev-kit` wizard (stored in ~/.claude/dev-kit-telemetry/config.json); this is a fallback toggle. When on, sessions where the kit runs send ANONYMOUS token counts to a relay (no key in the client, no prompts/code/paths/emails/org-instance/IP). See TELEMETRY.md. Hard off: DEVKIT_TELEMETRY=0.",
      "default": false,
      "required": false
    }
  }
}

Contents

What it installs

The manifest is a name and a version. 1 skill, 5 commands, 9 agents, 3 hooks, 3 MCP servers, 1 plugin travel with it, and installing the plugin installs all of them — 820 tokens a session between them. Each is measured on its own page, and each can be installed alone.

Files

What ships with it

1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

marketplace.json 424 B

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.

17d ago Changed b87422cedffd
22d ago Changed 2ce2c8f04ea1
23d ago Changed b7b0bce6c02e
1mo ago Changed 759a807824cb
1mo ago Changed 1099dae11a4b
1mo ago First seen · 34 lines scan A e8d1dd3c1fe9

Subscribe to this mod's changes

fullstack-dev-kit is a plugin published in the GitHub repository theam/claude-dev-kit (15 stars, last pushed 18d ago), licensed Apache-2.0. 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.

Claude Code Code review Git and workflow Project management ai-agents claude-code-plugin developer-tools jira

workbench

Ticket-to-PR development workflow: triage, plan with verified citations, implement inside the plan, review, commit, PR. Pluggable issue trackers (Jira, Azure DevOps, GitHub Issues) or a backlog in the repo, so it works with no tracker at all.

matheusPavaneli/workbench · not measured

slopstop

Autonomous, ticket-anchored AI development for GitHub Issues, Linear, and JIRA, built on one idea: stop slop before it goes in, instead of reviewing it out afterwards. Work starts from a ticket, not a prompt. One command drives the whole lifecycle for one ticket or twenty at once, interleaved and unattended…

iansmith/slopstop · not measured

review

PR review, interactive git diff annotation review, and writing style guide.

umputun/cc-thingz · not measured

han-linear

Linear-facing extensions to the Han suite. Adds work-items-to-linear, which creates one Linear issue per slice from a work-items file. Works through the Linear MCP server and requires it to be configured. Depends on no other Han plugin. Opt-in: installed on its own, not pulled in by the han meta-plugin.

testdouble/han · not measured

han-github

Github specific extensions to the Han plugin for agentic planning and coding. Provides skills to post code reviews as PR comments, update a PR description with a consistent format, etc.