fullstack-dev-kit

Plugin fullstack-dev-kit from marketplace claude-dev-kit in theam/claude-dev-kit. Commands read from the repo's manifest — 2 days ago.

Skills (14)

• 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

• 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.

• delegate-backlog

  Delegate an approved backlog to the configured async provider so several stories are worked in parallel — one branch and PR per issue — then re-apply the kit's quality via pr-review/fix-pr. The provider is delegation.provider in the kit config (github-copilot or self-hosted-action). Verifies that pr

• 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

• 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 clos

• 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

• 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 user

• 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. Elaborates progressively (guided, the default) or in one shot (`--quick`). Supports Jira, Linear, GitHub Issues, and

• plan-definition

  Turn a spark (an idea, even a one-liner, in any format) into a clear product definition through a guided, Socratic discovery phase — frame the problem (users, outcome, metrics, constraints, non-goals), explore 2–4 directions with trade-offs, and produce an approved definition that then feeds plan-ba

• 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.

Slash commands (5)

• /fullstack-dev-kit:delegate-backlog

  Delegate an approved backlog to the configured async provider (github-copilot or self-hosted-action), then review the resulting PRs with the kit. Trades the in-session gates for throughput; nothing auto-merges. Usage - /delegate-backlog <issue numbers | parent/epic issue>

• /fullstack-dev-kit:launch-story

  Create a dedicated worktree for a story and open a new VS Code window on it, ready to run the pipeline. Usage - /launch-story PROJ-1234

• /fullstack-dev-kit:plan-backlog

  Turn an idea, brief, or document into a well-formed backlog and create it in your tracker after approval. Guided by default; --quick for a one-shot draft. Usage - /plan-backlog <idea text | path/to/brief.pdf | URL> [--quick]

• /fullstack-dev-kit:plan-definition

  Turn a spark (an idea, even a one-liner) into a clear product definition through a guided discovery phase, then hand it to plan-backlog. Facilitate, never decide. Usage - /plan-definition <idea text | path/to/brief.pdf | URL>

• /fullstack-dev-kit:work-story

  Work a user story end to end — fetch the ticket, plan, implement, verify gates, and open the PR. Usage - /work-story PROJ-1234 [--auto-approve]

Subagents (9)

• backlog-delegator

  Async fan-out orchestrator. Given an approved backlog of GitHub issues, it follows the delegate-backlog skill — the configured provider (github-copilot or self-hosted-action) verifies, enriches, triggers, and reads back one branch and PR per issue. Tracks the run and re-applies the kit's quality via

• backlog-planner

  Product-owner orchestrator. Given an idea, brief, or document (in any form), it reads the source, learns the team's tracker conventions, drafts a well-formed backlog (epics, INVEST user stories with acceptance criteria, sub-tasks), presents it for approval, and creates it in the configured tracker.

• coding-agent

  Orchestrator for the issue-to-PR workflow. Given a user story ID (e.g. PROJ-1234, ENG-42, #123), it fetches the ticket and any linked Figma designs, presents a plan for approval, coordinates implementation, enforces the coverage and e2e gates, self-reviews, and opens the PR.

• coverage-guardian

  Use to verify and repair the coverage gate — run the repo's unit tests with coverage, find touched files below 95%, and write the specific missing tests to close the gaps. Language- and framework-agnostic.

• e2e-author

  Use to create or update end-to-end tests for user-facing flows changed by a story, using the repo's existing e2e framework, including realistic edge cases, and to run them until green.

• plan-definer

  Product-owner discovery orchestrator. Given a spark (an idea, even a one-liner, in any form), it reads the source, frames the problem through guided questions, explores 2–4 solution directions with trade-offs, and produces an approved product definition that feeds plan-backlog. Facilitates the PO's

• pr-fixer

  Use to resolve findings on an existing pull request - review comments, CI failures, and self-review findings - fixing code, updating tests, re-verifying gates, and pushing. The counterpart to pr-reviewer that closes the loop.

• pr-reviewer

  Use for high-signal review of a diff or pull request in any codebase, with emphasis on scope (PR intent), correctness, contract drift, security, performance/duplication introduced, and the project's test/coverage gate.

• security-reviewer

  Use for a focused security pass on a diff or pull request - authorization, secrets, input validation, data exposure, webhook verification, and OWASP-style concerns. Runs as part of the coding-agent verify step and on demand.

MCP servers (3)

• atlassian

  connects to: https://mcp.atlassian.com/v1/mcp

• linear

  connects to: https://mcp.linear.app/mcp

• figma

  connects to: https://mcp.figma.com/mcp

Hooks (3)

• SessionStart

  node "${CLAUDE_PLUGIN_ROOT}/scripts/telemetry.mjs"

• Stop

  node "${CLAUDE_PLUGIN_ROOT}/scripts/telemetry.mjs"

• SessionEnd

  node "${CLAUDE_PLUGIN_ROOT}/scripts/telemetry.mjs"

Similar plugins