install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/implementing" ~/.claude/skills/majiayu000-claude-skill-registry-implementing && rm -rf "$T"
manifest:
skills/data/implementing/SKILL.mdsource content
Implementing
Overview
Execute an existing plan exactly as written, with verification and checkpoints. If the plan is wrong or unclear, stop and ask to change it.
When to Use
- A plan document exists and is approved
- The work needs disciplined, step-by-step execution
Skip if: there is no plan (write one first) or the task is trivial.
Quick Reference
- Read the full plan.
- Call out blockers or questions.
- Track progress per task.
- Verify each task before moving on.
- Check in after a small batch.
Execution Workflow
-
Load the plan
- Read end to end.
- Identify unclear steps or missing info.
-
Confirm before starting
- If anything is unclear, ask and wait.
- Do not "fix" the plan silently.
-
Execute tasks in order
- One task at a time.
- Follow steps exactly.
- Run the listed verification.
- Mark the task complete.
-
Checkpoint
- After 2-3 tasks (or any risky task), summarize:
- What changed
- Verification results
- Open questions
- Wait for approval before continuing.
- After 2-3 tasks (or any risky task), summarize:
-
Finish
- Run any final verification from the plan.
- Report completion and remaining risks.
Rules
- Do not add scope or extra features
- Do not reorder tasks unless the plan says so
- Stop and ask if blocked or if verification fails
Common Mistakes
- Skipping verification to "save time"
- Changing the plan without approval
- Executing multiple tasks in parallel without permission