Claude Code Plugins

A collection of plugins for Claude Code, Anthropic's CLI for Claude.

Installation

Add this marketplace to Claude Code:

/plugin marketplace add schuettc/claude-code-plugins

Then install any plugin:

/plugin install <plugin-name>@schuettc-claude-code-plugins

Available Plugins

Plugin	Description	Version
project-workflow	One-shot setup for a new repo's standards: feat → dev → main promotion model + PR CI gate, GitHub repo setup (branch protection, environments, secrets, OIDC), and the language-agnostic quality stack. /project-init detects current state and applies only the gaps — new or existing repos — plus a multi-repo workspace on-ramp. Setup-only and disposable; pulls in the evergreen plugins as dependencies	0.2.1
engineering-standards	Evergreen engineering standards consulted while writing/reviewing code: GitHub API discipline (zipball over per-file, rate-limit backoff), worktree isolation + location rule (worktrees at the target repo's .worktrees/, never /tmp), with automation-auth and hook-escape conventions on the way. Pure advisory, no tooling — safe to leave enabled forever	0.1.2
feature-workflow	Feature lifecycle with directory-based tracking, state overlay (paused / replaced / abandoned), epic dispatch via /feature-autopilot, per-feature review override (external / internal / skip), event-driven hooks, and automated PR reviews via Gemini/Codex/OCI in GitHub Actions. Scales to multi-repo workspaces: aggregated cross-repo dashboard, cross-repo epics, contract-edit warnings, and coordinated producer-first deploy (/feature-deploy). Merge-queue-aware ship + a preflight CI-parity gate before every push	9.13.0
quality-workflow	Sister to feature-workflow for static-analysis findings. Surfaces, triages, and resolves skylos (Py) / fallow (TS) output. /quality-verify-hook self-tests pre-commit hooks against known-bad fixtures (catches the silently-misconfigured-hook class of bug). /quality-audit produces fingerprinted snapshots + diff (active counts only). /quality-unblock triages failing hooks; refuses bare suppressions. Plus the language-agnostic suppression-discipline standard	0.3.0
website-deployment	Guided workflow to deploy Node.js/Express apps to AWS serverless (S3 + CloudFront + Lambda + API Gateway + CDK). Analyzes your app, scaffolds infra, and deploys with step-by-step explanations	1.0.0
sprint-planner	Sprint planning and team coordination for small teams (2-6 devs). Triage backlogs by deadline, assign work with self-service specs, audit specs for completeness, and generate team communication. Pairs with feature-workflow	0.1.0
ghost	Draft, revise, and push blog posts to a Ghost site from Claude Code. Learns your writing voice from your published posts (or a short interview) into a living style guide, drafts in it, revises section by section against an anti-patterns list, and pushes to Ghost as a draft — publishing stays a manual action in Ghost. Bundles the ghost-blog-mcp Admin API MCP server	0.1.2

Bringing a project up to standard

These plugins compose — each owns one phase of a project's life (setup → standards → quality → features → planning). For the full walkthrough of adopting them on a new or existing project, how they hand off to each other, and which one is safe to disable when its job is done, see ADOPTION.md.

Plugin: feature-workflow

Structured feature development from idea to production, with draft-PR review gates and optional automated review by an external AI (Gemini or Codex) in GitHub Actions.

Setup:

• /feature-init — one-time project setup. Choose a reviewer (gemini / codex / none), drop in an API key, and the skill writes the workflow, prompts, and post-review.sh to .github/, uploads the secret, and enables bot PR approvals.
• /feature-init --workspace — scaffold a multi-repo workspace (coordinate several interconnected repos in one org as one). See Multi-repo workspaces below.

Lifecycle:

• /feature-capture — capture a feature idea to docs/features/<id>/idea.md
• /feature-plan <id> — produce plan.md with requirements, design, and an implementation breakdown
• /feature-review-plan <id> — open a draft PR and trigger plan review; --respond replies inline on review threads
• /feature-implement <id> — implement the approved plan with scope guarding
• /feature-review-impl <id> — trigger impl review on the same PR; --respond replies inline
• /feature-ship <id> — run security + QA gates, merge the PR, and write shipped.md

Diagnostics:

• /feature-status — snapshot of the dashboard
• /feature-audit <id> — evidence-based runtime verification
• /feature-troubleshoot — structured debugging for shipped features

Install:

/plugin install feature-workflow@schuettc-claude-code-plugins

See feature-workflow/README.md for full documentation.

Multi-repo workspaces

When several repos in one org are developed together, set up a workspace — a thin coordination repo with each member nested inside it as an independent, gitignored clone (not a submodule). Launch Claude at the workspace root: every member is in the tree, so cross-repo edits never prompt, yet each member stays its own git repo.

• Set it up: /feature-init --workspace --org <org> --member <dir>=<owner/repo> … (or let /project-init offer the on-ramp).
• Single-member feature → cd <member> and use the normal flow.
• Cross-repo feature → an epic in the workspace, one child per member (repo:id); /feature-autopilot <epic> dispatches each child into its member.
• Contracts drive producer-edit warnings; deploy groups drive /feature-deploy (producer-first).
• The dashboard auto-aggregates across the workspace and all members.

Day-to-day model: feature-workflow/skills/shared/workspace.md. Design: docs/designs/2026-06-08-multi-repo-workspace.md.

Plugin: website-deployment

Deploy a local Node.js / Express / Vite web app to AWS serverless infrastructure, guided step-by-step. Claude analyzes your app, explains what needs to happen, scaffolds the infrastructure, and walks you through each decision.

What it handles:

• Static frontend hosting via S3 + CloudFront
• Server-side routes converted to Lambda functions behind API Gateway
• DynamoDB for data
• Cognito for authentication
• Infrastructure as code via AWS CDK
• Cost awareness — most dev-traffic deployments fit in the free tier

Bundled MCP servers (start automatically): AWS Documentation for live docs lookups, and Playwright for end-to-end browser testing of the deployed app.

Prerequisites: Node.js 18+, AWS CLI v2 with credentials, Python + uvx (for the AWS docs MCP server).

Install:

/plugin install website-deployment@schuettc-claude-code-plugins

See website-deployment/README.md for prerequisites, usage, and teardown instructions.

Plugin: sprint-planner

Sprint planning and team coordination for small teams (2-6 devs) with mixed experience levels preparing for demos, releases, or time-boxed sprints. Turns a messy backlog into an actionable sprint plan with assignments that developers can work from independently.

Skills:

• /sprint-triage — clean up the backlog; close stale items, verify PR status, categorize by deadline
• /sprint-plan — create a weekly sprint plan; triage backlog, assign owners, identify critical path
• /sprint-audit-specs — audit feature specs for completeness so devs can work independently
• /sprint-assign — generate a shareable team assignment message for Slack/email
• /sprint-retro — end-of-sprint review; planned vs. actual, lessons learned

Pairs with feature-workflow: reads docs/features/DASHBOARD.md and feature idea files. Use /feature-capture to add items, /feature-plan to start work, /feature-ship to close them.

Prerequisites: Git repository with feature tracking (e.g., docs/features/DASHBOARD.md from feature-workflow), GitHub CLI (gh) for PR status checks.

Install:

/plugin install sprint-planner@schuettc-claude-code-plugins

See sprint-planner/README.md for the full workflow and design principles.

Plugin: ghost

Draft, revise, and push blog posts to a Ghost site — directly from Claude Code. The plugin learns your writing voice from your published posts (or a short interview when you're starting out), keeps it in a living style guide, and drafts in that voice — then revises section by section and pushes to Ghost as a draft. Publishing stays a deliberate human action in the Ghost UI.

Setup:

• /ghost:setup-ghost — connect your Ghost site (writes a gitignored .claude/ghost.creds.json and verifies the MCP connection). Run once per repo.
• /ghost:build-style-guide — learn your voice from your published posts, or /ghost:define-voice to seed it from a short interview when you don't have a corpus yet.

Draft → revise → push:

• /ghost:draft-post — plan an angle and draft a full post in your voice, self-audited against the anti-patterns.
• /ghost:revise-post — walk the draft section by section (formatting, voice, accuracy).
• /ghost:push-draft — push to Ghost as a draft via the Admin API. Never publishes.
• /ghost:write-post — run the whole flow (draft → revise → push) in one guided pass.

Bundled MCP: the ghost-blog-mcp Ghost Admin API server, fetched automatically via npx — 7 tools covering post/page CRUD, tags, images, and site metadata.

Install:

/plugin install ghost@schuettc-claude-code-plugins

See ghost/README.md for the full skill reference and credential setup.

Cloning This Repo? Start Here

If you cloned this repo and want Claude to walk you through installing and using feature-workflow in your own project, open Claude Code in this repo and run:

/getting-started

It's a local skill defined in .claude/skills/getting-started/SKILL.md — not shipped with the plugin. It orients you to what this repo is, helps you install the plugin from this marketplace, and can drive a live end-to-end demo feature (capture → plan → review → implement → review → ship) against a project of your choice so you see the whole lifecycle before touching real work.

Development Mode

To test plugins locally:

git clone https://github.com/schuettc/claude-code-plugins.git
claude --plugin-dir ./claude-code-plugins/<plugin-name>

License

MIT