Cp Explore
Productivitycp-exploreCp Explore is an Agent Skill for productivity published in the tangziwen/CubeMiniGame repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Explore and clarify a prospective CodePlan before writing design.md. Use when the user has a rough requirement and wants read-only investigation, clarifying questions, constraints discovery, and a compact candidate CodePlan name before running cp-plan.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/tangziwen/CubeMiniGame/blob/HEAD/.agents/skills/cp-explore/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cp-explore, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
CodePlan Explore
Shared Contract
Before acting, read ../_shared/codeplan/core.md.
Purpose
Clarify the user's intent before creating or updating a CodePlan. This is the read-only "grill me" phase.
Do not create, edit, delete, move, format, stage, commit, or generate files while using this skill. Only read files and ask or answer questions.
Workflow
- Read project instructions such as
AGENTS.md. - Restate the user's rough requirement in one or two sentences.
- Inspect only the repository areas needed to understand the problem.
- Identify existing
CodePlan/directories that may be related. - Ask focused clarifying questions when the plan would otherwise be ambiguous.
- Suggest one compact PascalCase CodePlan directory name.
- When the requirement is clear enough, tell the user the next step is
cp-plan.
Read-Only Rules
Allowed:
- list files
- read files
- search with
rg - inspect git status or diffs
- summarize architecture and risks
Forbidden:
- editing any file
- creating
CodePlan/<Name> - updating
design.md - updating
progress.md - running formatters
- compiling or building
If the user asks to make changes during exploration, stop and recommend switching to the appropriate next skill.
Questions
Ask only questions that materially affect the plan. Prefer a short list.
Good questions identify:
- desired behavior or final architecture
- hard constraints and non-goals
- risky compatibility expectations
- whether old code should be preserved or removed
- whether the work should be phased for cheaper models
Output
End with:
- a concise requirement summary
- key constraints and non-goals
- open questions, if any
- candidate CodePlan name
- whether the user should proceed to
cp-plan
Do not write a design document in this phase.