commit
Selectively stages and commits only the changes related to the current session, skipping unrelated modifications.
Quick gut-check before implementing when the user directly asks you to do something (e.g. "add X", "fix Y", "change Z"). Investigates, proposes a lightweight plan, and implements after approval. Use this instead of /create-plan when the user wants something done, not a formal
$ npx -y skills add dcouple/Pane --skill simple-plan --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/simple-planContext preview
The summary Claude sees to decide when to auto-load this skill.
Quick gut-check before implementing when the user directly asks you to do something (e.g. "add X", "fix Y", "change Z"). Investigates, proposes a lightweight plan, and implements after approval. Use this instead of /create-plan when the user wants something done, not a formal
name: simple-plan description: Quick gut-check before implementing when the user directly asks you to do something (e.g. "add X", "fix Y", "change Z"). Investigates, proposes a lightweight plan, and implements after approval. Use this instead of /create-plan when the user wants something done, not a formal plan. argument-hint: "[what the user wants done]" allowed-tools: Read, Grep, Glob, WebFetch
When the user directly asks me to make a change, I will first investigate and propose a plan before implementing anything. This ensures alignment before any code is written.
Feedback from a principal engineer perspective, providing overall architectural and implementation guidance.
1. Investigate the codebase first 2. Present the plan to the user 3. **Only when the user approves** will I proceed 4. After approval, prefer one primary `implementer` sub-agent to execute the whole plan rather than fragmenting it by default 5. Keep the user's stated why, constraints, and non-goals explicit during implementation rather than letting the task list silently replace them 6. After implementation, run the Claude `implementation-reviewer` and Codex review in parallel when the plugin is available, and wait for both before declaring completion 7. If the Codex plugin is unavailable, run the Claude `implementation-reviewer` alone before declaring completion
User Query: $ARGUMENTS
Repo: dcouple/Pane
Selectively stages and commits only the changes related to the current session, skipping unrelated modifications.
Creates a reconciled implementation plan by combining a structured plan draft with a normalized intent brief and a PRP-style research dossier, then…
Have an interactive discussion about a topic, approach, or feature. Researches the codebase as needed, talks through options, and updates ./tmp/context.md with…
Executes an approved plan with one primary implementation stream by default, using bounded parallel sidecars only when the write scopes are truly disjoint.…
Investigates bugs through hypothesis-driven root cause analysis. Automatically invoked when the user reports a bug, error, broken behavior, or something not…
Commits changes grouped by done-plans, rebases main, runs build and quality gates, then creates or updates a PR. Replaces the commit command. Use when you're…