website-deployment v1.0.0

Initial release of the website-deployment plugin — a guided workflow to deploy local Node.js / Express / Vite web apps to AWS serverless infrastructure.

What it does

Claude analyzes your app, explains what needs to happen, and walks you through each decision. Depending on your app, that might include:

• Hosting static files via S3 + CloudFront
• Converting server-side routes to Lambda functions behind API Gateway
• Adding a database with DynamoDB
• Adding authentication with Cognito
• Managing everything as infrastructure-as-code with CDK

Bundled MCP servers

• AWS Documentation — search and read official AWS docs during deployment
• Playwright — end-to-end browser testing of the deployed app

Install

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

Prerequisites

• Node.js 18+
• AWS CLI v2 with credentials configured
• Python + uvx (for the AWS Documentation MCP server)

Most dev-traffic deployments fit in the AWS free tier. Claude explains cost implications as resources are created and can tear everything down when you're done.

See website-deployment/README.md for full documentation.

sprint-planner v0.1.0

Initial release of the sprint-planner plugin — 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, well-documented sprint plan with team assignments that developers can work from independently.

Skills

Skill	Command	Purpose
Sprint Triage	/sprint-triage	Clean up the backlog — close stale items, verify PR status, categorize by deadline
Sprint Plan	/sprint-plan	Create a weekly sprint plan — triage backlog, assign owners, identify critical path
Sprint Audit Specs	/sprint-audit-specs	Audit feature specs for completeness — ensure devs can work independently
Sprint Assign	/sprint-assign	Generate a shareable team assignment message for Slack/email
Sprint Retro	/sprint-retro	End-of-sprint review — planned vs. actual, lessons learned

Typical workflow

/sprint-triage          # Clean up backlog, close stale items
/sprint-plan            # Create the sprint plan with assignments
/sprint-audit-specs     # Verify specs are complete for all assignees
/sprint-assign          # Generate team message
... [sprint happens] ...
/sprint-retro           # Review outcomes, capture lessons

Design principles

• Verify state before planning — check PR status, branch state, and recent merges before assuming work needs to be done.
• Single source of truth — one backlog, one dashboard. Consolidate duplicates immediately.
• Self-service specs for junior devs — every assigned task needs enough context for independent work.
• Critical path first — blocking work to senior devs, parallelizable leaf work to junior devs.
• Triage by deadline, not priority — a P1 isn't deadline-critical if the deadline is a demo and the feature isn't demo-relevant.
• Don't create tracking artifacts — reuse feature-workflow's DASHBOARD.md instead of adding new tracking systems.

Pairs with feature-workflow

Reads docs/features/DASHBOARD.md and feature idea files from the feature-workflow plugin. Use /feature-capture to add new items, /feature-plan to start work, /feature-ship to close items.

Install

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

Requirements

• Git repository with feature tracking (e.g., docs/features/DASHBOARD.md from feature-workflow plugin)
• GitHub CLI (gh) for PR status checks
• A backlog with feature idea files to triage and assign

See sprint-planner/README.md for full documentation.

feature-workflow v9.2.0

Major release introducing automated PR reviews via GitHub Actions, plus inline thread reply/resolve flows and tighter reviewer prompts.

Spans everything since v2.4.1. The plugin now handles the full capture → plan → review → implement → review → ship lifecycle with an optional external AI reviewer (Gemini or Codex) running in CI.

9.2 — Inline thread replies + tighter prompt filters

• Inline responses on resolved findings — /feature-review-plan <id> --respond and /feature-review-impl <id> --respond fetch review threads via GraphQL, reply inline on each finding with Resolved in <sha>: <one-line>, and resolve the thread via the resolveReviewThread mutation. Disagreed findings get an inline reply explaining the reasoning but stay open.
• Visible ### Verdict: heading — review prompts now require a display verdict heading in the markdown body, so the posted review shows PASS / CONDITIONAL PASS / FAIL prominently (independent of the machine-readable prefix that the workflow strips).
• No-op finding filter — prompts explicitly reject "no change required, just confirming" commentary, hedged hypotheticals, and defensive additions for impossible conditions.

9.1 — Workflow-side review posting

• Reviewer no longer runs gh commands — Gemini/Codex output structured text (verdict line, markdown body, inline-comments JSON block between sentinels) and the workflow itself parses and posts via gh pr review and gh api pulls/N/comments.
• Line-anchored inline comments — reviewers emit a JSON array between <!-- INLINE_COMMENTS_JSON --> sentinels; post-review.sh loops through them and posts each as a line-anchored review comment on the diff.
• New templates/post-review.sh installed into .github/scripts/ by /feature-init and /feature-init --update.

9.0 — Automated PR reviews

• Gemini + Codex in GitHub Actions — draft PRs auto-reviewed by an external AI. Submit skills add plan-review / impl-review labels that trigger the workflow; ship removes them. synchronize re-runs review on every push.
• /feature-init --update — refresh the generated CI workflow, review prompts, and post-review.sh in an existing project without re-running full init or re-uploading your API key.
• Bot approval setup — feature-init automatically enables the repo-level "Allow GitHub Actions to approve pull requests" setting so PASS verdicts land as approvals.
• Plan review step added — /feature-review-plan opens a draft PR with idea.md + plan.md before implementation, gated by plan-stage review.
• Configurable branch naming — .feature-workflow.yml controls branch prefix and target branch.

Upgrade

/plugin marketplace update schuettc-claude-code-plugins

Then in each consumer project:

/feature-init --update

This refreshes .github/workflows/feature-review.yml, review prompts, and post-review.sh. It does not touch .feature-workflow.yml, your uploaded API secret, or docs/features/. Commit and push the refreshed files to your default branch.

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

feature-workflow v2.4.1

Fix: Add Command Wrappers for Slash Menu

Patch release that adds thin command wrapper files so /feature-* commands appear in the slash menu autocomplete.

Changes

• Added commands/ directory with wrapper files that reference skills
• Updated plugin.json to include "commands": "./commands/"
• Each command file has frontmatter for slash menu + reference to skill

Structure

commands/
├── feature-capture.md      → skills/feature-capture/SKILL.md
├── feature-plan.md         → skills/feature-plan/SKILL.md
├── feature-ship.md         → skills/feature-ship/SKILL.md
├── feature-audit.md        → skills/feature-audit/SKILL.md
└── feature-troubleshoot.md → skills/feature-troubleshoot/SKILL.md

This fixes the issue where skills weren't appearing in slash command autocomplete after the v2.4.0 migration.

feature-workflow v2.4.0

Migrate Commands to Skills Format

Major structural change that converts all 5 workflow commands to the skills format for better auto-discovery and consistent plugin architecture.

What Changed

Structure Migration:

• Workflow content moved from commands/ to skills/ directories
• Thin command wrappers in commands/ reference the skills (for slash menu visibility)
• Sub-phase files are now plain markdown (frontmatter removed)

Final Structure:

feature-workflow/
├── commands/                    # Thin wrappers for slash menu
│   ├── feature-capture.md
│   ├── feature-plan.md
│   ├── feature-ship.md
│   ├── feature-audit.md
│   └── feature-troubleshoot.md
└── skills/                      # Full workflow content
    ├── feature-capture/SKILL.md
    ├── feature-plan/SKILL.md + 4 phase files
    ├── feature-ship/SKILL.md + 4 phase files
    ├── feature-audit/SKILL.md + 7 phase files
    ├── feature-troubleshoot/SKILL.md + 5 phase files
    └── [6 existing context skills unchanged]

User Experience

• Slash commands work: /feature-plan, /feature-capture, etc. appear in autocomplete
• Auto-suggestion enabled: Claude can proactively suggest workflows based on context
• Enhanced descriptions: Each skill includes trigger hints for better discovery

Breaking Changes

None - backwards compatible. All /feature-* commands work as before.

---

Note: Use v2.4.1 for the complete fix including command wrappers.

feature-workflow v2.0.0

What's New

Claude Agent Skills Best Practices Alignment

• Renamed all 5 skills to gerund form for clarity
• Split long commands using progressive disclosure (feature-plan: 722→159 lines, feature-ship: 520→117 lines)
• Added hooks for atomic backlog status transitions

Terminal Context Identification

• Added status line setup instructions for identifying which feature you're working on
• Works with dotfiles status line script

Documentation

• Added TOC to all files > 100 lines
• Trimmed verbose templates, added input/output examples