Mission Kit
A simple framework with built-in Project Management, DevSecOps, and full agent orchestration to plan, build, review, and ship anything to the real world without leaving the IDE.
Timelapse: one hour of real coding with Mission Kit
Mission Kit prompt handles setup end to end. If you like adventure, use the CLI: run npx @dadado/agent-kit-cli install in your project root, then agent-kit to check commands. Light setup with local files only and nothing global touched.
npx @dadado/agent-kit-cli install
Add files to a repo, open a new chat, and run /agent-kit-onboard. agent-kit reads your codebase and customizes rules, skills, commands, and dependencies for your stack. It also helps you set up Git flow, CI/CD, variables, secrets and more.
Time for some action: /start-project with a goal. agent-kit invokes the PO to check previous work and context before planning anything. You choose whether to add the task to the backlog or execute the plan all the way.
No fancy graphs or Jarvis bros loops. There are three levels of autonomy for agent teams: run single plans with /continue-plan to control every step; /run-plan asks the team to execute autonomously; /run-plan-all in a fresh window lets agent-kit Scrum Master handle planning and execution.
Manage projects directly in the development flow. /backlog-add as many tasks as you want, then type /run-plan-all and let the PO organize, drop, merge, and queue tasks into a single execution plan. Approve the queue, go get a coffee.
After each plan completes, agent-kit arms an external review: a second agent audits your deliverables against acceptance criteria, checks for regressions, and files its findings in the Field Report. /plan-review-triage lets you choose: write a residuals plan, fix nits inline, or acknowledge and move on. Mid-batch reviews run between queued plans so nothing compounds silently. You review findings, not diffs.
/plan-review-triageTriageEvery completed phase runs the repository's formatter and linter before staging. Pass? Agent-kit commits with Conventional Commits, pushes a working branch, opens a merge request to staging, and merges it. One topic, one MR, zero manual git. /git-prod promotes approved staging to production after an explicit confirmation gate. Direct commits to main are blocked by convention and by hook.
Every mission has a cockpit. Invoke yours with /dashboard and have instant observability on what's happening from any browser.
Mission Kit 5 packs a complete toolbox that makes painful work easy and a set of dashboards that make everything visible.
Decisions (ADR-lite), resolved errors, review audits, and the consolidated index. What the team learned persists across sessions, searchable by tag, date, or theme.
A fixed check set: plans, HANDOFF freshness, agents, commands, memory, git, config. Each failing check ships its own fix hint. Green means go. Red tells you exactly what to touch.
Staging vs production diff, recent merges, branch state, and hook status. See what's ahead of main, what's queued for prod, and whether your guards are active.
Every Agent Skill discovered under .cursor/skills/, with kit-managed and editable ones told apart. Drop in a SKILL.md and it shows up here.
The full slash-command inventory: what each does, which are yours to edit, and a copy-ready prompt to create new ones. No digging through .cursor/commands/ to remember what's installed.
See what's happening as you go: easy to browse active terminals, processes, git, agents and all the runtime at the tip of a finger.
The Config tab tunes cooldowns between ticks, audit preferences, agent persona, and external review behavior. Everything persists in a single config.json. Run agent-kit update to pull the latest commands, templates, and dashboard without losing your customizations.
Agent Kit is dogfooded daily. Every feature ships through the same /start-project to /git-prod pipeline it provides. Plans, reviews, triage, staging: the framework that builds your projects is built with the framework. Dogfood reports live under dogfood/ as real CI evidence.
Mission Kit 5 reads the same plain files in .cursor/ that your agents write, so what you see is what's actually on disk.