Create Plan
Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.
Install
$ agentstack add skill-zhangtuansia-agent-operator-create-plan ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-zhangtuansia-agent-operator-create-plan) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Create Plan
Goal
Turn a user prompt into a single, actionable plan delivered in the final assistant message.
Minimal workflow
Throughout the entire workflow, operate in read-only mode. Do not write or update files.
- Scan context quickly
- Read
README.mdand any obvious docs (docs/,CONTRIBUTING.md,ARCHITECTURE.md). - Skim relevant files (the ones most likely touched).
- Identify constraints (language, frameworks, CI/test commands, deployment shape).
- Ask follow-ups only if blocking
- Ask at most 1–2 questions.
- Only ask if you cannot responsibly plan without the answer; prefer multiple-choice.
- If unsure but not blocked, make a reasonable assumption and proceed.
- Create a plan using the template below
- Start with 1 short paragraph describing the intent and approach.
- Clearly call out what is in scope and what is not in scope in short.
- Then provide a small checklist of action items (default 6–10 items).
- Each checklist item should be a concrete action and, when helpful, mention files/commands.
- Make items atomic and ordered: discovery → changes → tests → rollout.
- Verb-first: “Add…”, “Refactor…”, “Verify…”, “Ship…”.
- Include at least one item for tests/validation and one for edge cases/risk when applicable.
- If there are unknowns, include a tiny Open questions section (max 3).
- Do not preface the plan with meta explanations; output only the plan as per template
Plan template (follow exactly)
# Plan
## Scope
- In:
- Out:
## Action items
[ ]
[ ]
[ ]
[ ]
[ ]
[ ]
## Open questions
-
-
- Checklist item guidance
Good checklist items:
- Point to likely files/modules: src/..., app/..., services/...
- Name concrete validation: “Run npm test”, “Add unit tests for X”
- Include safe rollout when relevant: feature flag, migration plan, rollback note
Avoid:
- Vague steps (“handle backend”, “do auth”)
- Too many micro-steps
- Writing code snippets (keep the plan implementation-agnostic)
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: zhangtuansia
- Source: zhangtuansia/agent-operator
- License: Apache-2.0
- Homepage: https://aicowork.chat
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.