REFERENCE
Best practices & FAQ
How to get the most out of the plugin day to day, and answers to the questions that come up first.
What you get
Pay for depth only when needed
Simple tasks carry zero ceremony; full workflows load only when you ask.
Task-level continuity
Corrections and omissions continue inside the same flow, with no re-invocation.
Approval is never implied
A separate, explicit human act separates understanding from doing.
Evidence-driven completion
Nothing counts as done without fresh, scope-appropriate verification.
Two hosts, one semantics
Codex CLI and Claude Code share synchronized invocation behavior.
Read-only where it matters
Review and handoff never touch your repository.
Day-to-day practices
- Use ordinary prompts for clear, routine tasks — naming a workflow adds cost you do not need.
- Name a workflow when you want its deeper process, and put the token on the first line.
- Read the checkpoint before approving. Approval is the one place where your attention pays the most.
- Treat repository docs and instruction files as domain truth — they always take priority over the plugin.
- Say what is out of scope. It is as useful as saying what you want.
- For material data, permission, or destructive decisions, name a full workflow instead of relying on the Core.
Frequently asked questions
Do I have to name a workflow for every task?
No — and you should not. The always-on Core already covers ordinary work. A full workflow changes the shape and cost of the session, so reach for one when you want its deeper process.
Why did it stop and wait even though my request was clear?
Invoking Develop is not approval to code. The checkpoint is a fixed step: it states the goal and boundary first, then pauses. Reply with action language such as “proceed with the plan above” and it continues.
Can it commit or push my work?
Not without authorization. Committing, pushing, publishing, opening issues, installing dependencies, and changing global configuration all require explicit permission from you.
Does the plugin override my project instructions?
No. Your current request, the project’s AGENTS.md or CLAUDE.md, and its authoritative documents always take priority. The workflows discover and consume your conventions; they do not replace them.
How do I stop a workflow that is still active?
Cancel it explicitly, switch to another workflow, or start an unrelated task. Any of the three ends the inheritance; a new unrelated task never inherits a stale workflow or approval.
Is there a way to see what actually ran?
Yes. Every workflow reports its evidence: which commands ran, what changed, and which acceptance behavior was verified, partially verified, incomplete, or deviated.