--- title: "fullstack-dev-kit" description: "Issue-to-PR workflow for any tech stack: fetch stories from Jira/Linear/GitHub/Azure and Figma designs, plan-approval gate, adaptive quality + coverage gates, e2e generation, PR creation and review." canonical: https://agentpluginsdirectory.com/plugins/fullstack-dev-kit last-updated: 2026-09-25 --- # fullstack-dev-kit Issue-to-PR workflow for any tech stack: fetch stories from Jira/Linear/GitHub/Azure and Figma designs, plan-approval gate, adaptive quality + coverage gates, e2e generation, PR creation and review. - Slug: fullstack-dev-kit - Publisher: The Agile Monkeys - Repository: https://github.com/theam/claude-dev-kit - Manifest: plugins/fullstack-dev-kit/plugin.json - Version: 0.19.17 - License: Apache-2.0 - Category (editorial): productivity - Skills: 13 (coverage-check, create-pr, dev-kit-setup, e2e-generate, figma-fetch, fix-pr, follow-ups, issue-fetch, issue-update, plan-backlog, plan-definition, pr-review, work-story) - MCP servers: 0 - Stars: 14 - Repository created: 2026-07-09 - Repository last pushed: 2026-09-23 - Publisher type: Organization - Listing: https://agentpluginsdirectory.com/plugins/fullstack-dev-kit - Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json ## What fullstack-dev-kit does, in the publisher's words An open-source Claude Code plugin by The Agile Monkeys: a stack-agnostic issue-to-PR workflow with enforced quality gates. Also runs on OpenAI Codex, Cursor, and other Agent Plugins 1.0.0 clients. The kit taking a ticket all the way to an opened PR (test project yardflow): https://github.com/user-attachments/assets/21afb5ab-b52b-4418-bf01-d247e8d73208 - In a session: /mcp → pick the server → complete the browser OAuth. From the terminal: claude mcp login atlassian. Already in Claude Desktop? claude mcp add-from-claude-desktop. - codex plugin add atlassian-rovo@openai-curated (Jira/Confluence) · linear@openai-curated · figma@openai-curated. - Plugin commands and skills are namespaced under /fullstack-dev-kit: (type / and search). Agents never appear in that list: invoke them in plain language or let the orchestrator delegate to them (/agents shows them). - work-story presents its implementation plan in the chat and waits for your explicit approval before writing any code. From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/theam/claude-dev-kit/HEAD/README.md ## Skills - coverage-check: Run the repo's unit tests with coverage and verify that every file touched in the current change keeps line, branch, and function coverage at or above 95%. Language- and framework-agnostic. Use before committing, before PR creation, or when the user asks about coverage. - create-pr: Create a branch, commit the work, and open a pull request for a completed user story, after all quality gates pass. Use when the user asks to open/create a PR or as the final step of the story workflow. - dev-kit-setup: First-use bootstrap for the dev kit. Detects the team's issue tracker, discovers what it can via MCP/CLI, asks only what cannot be discovered, and persists the result to.claude/dev-kit.json in the consuming repo. Use when that file is missing, when the user asks to set up or reconfigure the kit, o… - e2e-generate: Create or update end-to-end tests for a user-facing flow that changed, using whatever e2e framework the repo already uses. Use after implementing a user story that alters UI behavior, routing, forms, or API-driven views. - figma-fetch: Extract frame/component structure and all visible text from a Figma design URL. Use whenever a prompt or a fetched issue contains a figma.com/design or figma.com/file link. - fix-pr: Resolve the findings on an existing pull request, review comments, CI failures, and self-review findings, driving each to a decision (fix / defer to a tracked issue / discard), re-verifying the gates, replying to each reviewer, and watching for late feedback. The counterpart to pr-review that clo… - follow-ups: Turn the loose ends a finished story leaves, out-of-scope notes, deferred review findings, deliberate TODOs, into tracked follow-up work items in the team's tracker, linked to the source story, after approval. Supports Jira, Linear, GitHub Issues, and Azure DevOps via adapters. Use at the end of… - issue-fetch: Fetch a work item (summary, status, description, acceptance criteria, comments) from the team's issue tracker and display a clean summary. Supports Jira, Linear, GitHub Issues, and Azure DevOps via adapters. Use whenever a prompt contains an issue reference (e.g. PROJ-1234, ENG-42, #123) or the use… - issue-update: Update the work item after delivery: comment the PR link and a product-facing summary, and transition it to the team's review status. Supports Jira, Linear, GitHub Issues, and Azure DevOps via adapters. Use right after a PR is created for a story, or when the user asks to update/move a ticket. - plan-backlog: Turn an idea or description (in any format) into a well-formed backlog, epics, user stories with acceptance criteria, sub-tasks, and create it in the team's tracker after approval. Supports Jira, Linear, GitHub Issues, and Azure DevOps via adapters. Use when a product owner wants to draft or crea… - plan-definition - pr-review: Structured review of a pull request or the current diff, correctness, contract drift, security, missing tests, coverage gate, producing classified findings and a verdict. Use when the user asks to review a PR or diff, or as the self-review step of the story workflow. - work-story: Work a user story end to end, fetch the ticket, plan (with approval), implement, verify the applicable gates, self-review, open the PR, and update the tracker. Use when given an issue key like PROJ-1234, ENG-42, or #123. This is the orchestration playbook for hosts without a dedicated orchestrator… Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.