AgentSlice – Make AI coding agents ask before they edit
AgentSlice is a free, open-source workflow kit that makes AI coding agents like Cursor, Claude Code, Codex, and Windsurf ask for approval before editing. It uses Markdown files to define phases and gates, preventing context drift, wandering edits, and unauthorized changes.
Article intelligence
Key points
- Open-source Markdown workflow kit for AI coding agents
- Enforces ask-plan-approve-build-QA-release cycle
- Compatible with Cursor, Claude Code, Codex, Windsurf and more
- No runtime or editor extension required
Why it matters
This matters because open-source Markdown workflow kit for AI coding agents.
Technical impact
May affect model selection, inference cost, product capability, and evaluation benchmarks.
Notifications You must be signed in to change notification settings
Fork 0
Star 0
BranchesTags
Open more actions menu
Folders and files
NameName
Last commit message
Last commit date
Latest commit
History
3 Commits
3 Commits
bin
bin
kit
kit
lib
lib
.gitignore
.gitignore
LICENSE
LICENSE
README.md
README.md
package-lock.json
package-lock.json
package.json
package.json
Repository files navigation
A free, open-source workflow kit for AI coding agents.
Makes Cursor, Claude Code, Codex and Windsurf ask before they edit.
Website • Discussions
Quick start
npx agentslice init
Paste INSTALL_PROMPT.md into Cursor / Claude Code / Codex / Windsurf
Watch the agent ask, plan, and wait
That's it. No build step, no runtime, no editor extension.
30-second demo
What it does
AI coding agents work better when they know the next step. Without a workflow they suffer from three failure modes developers describe constantly:
Context drift — the agent forgets what was decided two messages ago and reopens settled questions.
Wandering edits — the agent expands the task, touches files you didn't ask about, and burns tokens on detours.
Editing without asking — the agent jumps straight to changes before you've approved a plan.
AgentSlice gives the agent a project-local workflow it actually reads: a tiny set of Markdown files that pin down the phases, the gates, and the next required action so the agent asks first, plans first, and waits for approval before it edits.
What's in the kit
File Purpose
INSTALL_PROMPT.md The one prompt you paste into your AI tool to bootstrap the workflow.
docs/planning/workflow-state.md Resumable state file — current phase, approved slice, QA status, next allowed action.
.agents/skills/ Shared planning skills: intake, slice planning, spec, QA gate, release, advance.
.cursor/rules/ Project rules for Cursor.
.claude/skills/ + CLAUDE.md Skills and project memory for Claude Code.
.codex/skills/ + AGENTS.md Skills and project rules for Codex.
.windsurf/rules/ + .windsurfrules Rules for Windsurf.
Everything is plain Markdown. You can read it, fork it, edit it for your stack.
Supported tools
Cursor · Claude Code · Codex · Windsurf · OpenCode · any agent that respects project-level rule files (AGENTS.md, CLAUDE.md, .cursor/rules/, .windsurfrules).
How it works
Ask → Plan → Approve → Build → QA → Release → Next
Ask. The agent asks up to five product questions and writes lightweight context.
Plan. It proposes a first slice — the smallest end-to-end vertical you can ship.
Approve. You approve, reject, or adjust the slice. The agent waits.
Build. Only after approval does the agent write code.
QA. The agent (or a QA subagent, where supported) checks the work and reports PASS / PASS WITH NOTES / FAIL.
Release. A release recommendation is written. You approve.
Next. The state file advances to the next slice. The loop repeats.
The state lives in docs/planning/workflow-state.md so the next agent session resumes from a real checkpoint instead of re-guessing.
Why this exists
I spent 3 months experimenting with building AI products and testing different workflows. This is the workflow that actually worked — intake questions, slice discipline, QA handoff, cross-tool consistency.
Why no runtime, why just Markdown
AgentSlice is deliberately not an editor extension, daemon, or hook system. Two reasons:
Portability. The same files work in Cursor, Claude Code, Codex, Windsurf, OpenCode, and any future agent that reads project rules. A runtime would lock you into one tool.
Honesty. No Markdown file can force an LLM to obey. The gates are soft — discipline through clarity, not enforcement. AgentSlice is up-front about this. The workflow is durable because it lives in your repo, not because it traps the model.
If you need hard enforcement, pair AgentSlice with Cursor's PLAN / ASK toggle or Claude Code's hooks. AgentSlice gives the agent the workflow; your tool of choice can add the gates.
Contributing
PRs, issues, and discussion are all welcome. See CONTRIBUTING.md for guidelines.
The fastest way to help: open an issue with the exact prompt + tool + transcript where AgentSlice misbehaved. Real failure transcripts are gold for tuning the rules.
License
MIT. Use it however you want — personal projects, client work, internal tooling, your own product. If you build something on top of AgentSlice, a link back is appreciated but not required.
Maintainer
Built and maintained by Espen Andreassen. Reach out at [email protected] or open a discussion.
Made in Norway. Opinionated. Free. MIT.
About
A Markdown workflow kit that makes Cursor, Claude Code, Codex and Windsurf ask before they edit.
Resources
Readme
License
MIT license
Uh oh!
There was an error while loading. Please reload this page.
Activity
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
No releases published
Packages 0
Uh oh!
There was an error while loading. Please reload this page.
Contributors
Uh oh!
There was an error while loading. Please reload this page.
Languages
JavaScript 100.0%