A tool-agnostic AI-assisted development framework template. Structured workflow (Spec → Plan → Implement → Review) with canonical protocols, agent definitions for Claude Code/Cursor, and a guided project setup.
Backlog stage. Creates one backlog work item from natural-language input with tracker destination detection and clarifying questions when needed. Usage: /add-backlog-item [optional brief description].
Merge all ready PRs in a parallel batch into the target base branch sequentially, auto-resolving trivial CHANGELOG and documentation conflicts, pausing for human input only on non-trivial conflicts, and running post-merge-cleanup for each successfully merged PR. Prints the merge plan for visibility but proceeds…
Graduate a completed integration branch (develop- ) to develop. Opens the graduation PR after confirming all sub-items are merged and getting human approval. Usage: /graduate-development.
After a development PR is merged, sync with origin, switch to the merged PR's base branch, pull, verify or delete the remote implementation branch, delete the local branch, and update the related issue in the issue tracker. Usage: /post-merge-cleanup [--base base-branch] [--pr merged-pr-number] [branch-name].
Prepare a release from develop. Creates the release branch, assembles changelog fragments into CHANGELOG, bumps version, opens PRs to main and develop, then skips release-branch reviewer loops while driving ready-for-regression + CI on the main PR before human merge. Usage: /prepare-release [version number, e.g.…
Run a retrospective analysis on completed work to identify process improvement opportunities. Usage: /retrospective [PR number | branch name | batch date].
Compatibility/advanced alias: resolve a native GitHub epic or explicit item list into a bounded workflow execution scope, with optional delegated review and merge gates. For the recommended starting point, use /run-work instead. Usage: /run-epic --epic | --items [, ...] [--base ] [--delegate-review] [--may-merge]…
Propose portfolio batches (scan-only). No-target scan produces a batch recommendation; all target invocations emit redirect guidance. No mutation in any mode. Usage: /run-work [ ...].
Sync framework updates from the upstream template into this project. Compares template files (local path or remote ref) against this project, shows a categorized diff for review, applies approved changes, and generates ready-to-use git instructions (branch + commit + PR). Run from the project root. Usage…
Plan Ready stage. Reads the approved spec (or work item brief for Refactor items) and codebase, resolves technical approach questions, then writes the implementation plan, runs its reviewer gate, and resolves PR readiness. Usage: /generate-implementation-plan [optional feature slug or dev folder path].
Spec Ready stage. Conducts an alignment conversation and writes the feature spec, then continues through reviewer gate, PR creation, and PR readiness. Usage: /generate-new-feature [optional brief description of the feature].
In Development stage. Implements a feature via Full Pipeline (with spec+plan), Refactor (plan only, no spec), Fast Track (bug/simple change), or Hotfix (critical production bug), then keeps the PR moving until reviewer and CI readiness are resolved. Usage: /implement-development [dev folder path | brief description of…
Run the implementation review gate by manually reviewing against REVIEW.md. Applies fixes directly for blocking/important issues. Usage: /review-code [optional file paths or patterns].
Run the spec review gate by manually reviewing against REVIEW.md. Applies fixes directly where possible. Usage: /review-spec [optional path to dev folder].
Initialize a new project from this template. Runs a guided conversation to generate all project-specific documentation (business domain, architecture, tech stack, best practices) and opens a setup PR.
★not rated 9 3d agoA36 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: