# Fullstack Dev Kit (ChatGPT Plugin) > Tickets to reviewed PRs - Type: plugin - Publisher: The Agile Monkeys - Categories: Development, Media & Entertainment - Website: https://chatgpt.com/plugins/plugins_6a82e3d1df508191bfffcec222b18433 - Open in ChatGPT: https://chatgpt.com/plugins/plugins_6a82e3d1df508191bfffcec222b18433 - Version: 0.19.10 - Listed: 2026-10-15 ## About Takes work from idea to shipped PR. For product owners, plan-backlog turns an idea or brief into a well-formed backlog (epics, user stories with acceptance criteria) in your tracker. For engineers, it takes a ticket (Jira / Linear / GitHub Issues / Azure) from plan-approval through implementation, adaptive tests/coverage, security and accessibility review, to an opened pull request — then offers to track any leftover follow-ups as linked tickets. Stack-agnostic; the tracker and PR host are configured per repo (connect the matching MCP, e.g. Atlassian for Jira). ## Install 1. **Add it in ChatGPT** Open Plugins in the ChatGPT sidebar (web or desktop), search for “Fullstack Dev Kit” and select +. You'll be asked to sign in to any connected service on first use. Then type @ in a chat to call it. ## 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, or when issue-fetch cannot resolve its configuration. - **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 closes the loop. - **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 a story, or when the user asks to track follow-ups. - **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, - **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 create tickets from an idea, brief, or document. - **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 ## Example prompts - "Work ticket PROJ-1234 end to end and open a PR" - "Review this diff for correctness, security, and missing tests" - "Draft a backlog from this brief and create the tickets" ## Related - [Superpowers](https://chatgptplugins.directory/plugins/superpowers.md): Plan, develop, and debug code - [Codex Security](https://chatgptplugins.directory/plugins/codex-security.md): Security scanning for your codebase - [Build Web Apps](https://chatgptplugins.directory/plugins/build-web-apps.md): Build frontend-focused web apps with generated assets, browser testing, payments, and... - [GitHub](https://chatgptplugins.directory/plugins/github.md): Triage PRs, issues, CI, and publish flows - [Figma](https://chatgptplugins.directory/plugins/figma.md): Figma design-to-code workflows - [Adobe](https://chatgptplugins.directory/plugins/adobe.md): Design, combine, and edit --- Source: https://chatgptplugins.directory/plugins/fullstack-dev-kit · Index: https://chatgptplugins.directory/llms.txt · Independent and community-run. Not affiliated with or endorsed by OpenAI. ChatGPT is a trademark of OpenAI.