controlled-implementation
About
This skill ensures implementation work follows approved designs in a strictly controlled, step-by-step manner. It prevents scope creep by requiring full understanding of all documents before starting and executing only one explicit task at a time. Use it when you need to enforce disciplined, traceable execution against a specification.
Quick Install
Claude Code
Recommended/plugin add https://github.com/majiayu000/claude-skill-registrygit clone https://github.com/majiayu000/claude-skill-registry.git ~/.claude/skills/controlled-implementationCopy and paste this command in Claude Code to install this skill
Documentation
Controlled Implementation Skill
Execute implementation work in a strictly controlled, step-by-step manner based on approved design and implementation documents, preventing scope creep, premature execution, and task skipping.
Preconditions (Must Read First)
Before starting any implementation, the agent MUST:
- Read and fully understand all referenced documents provided by the user (design specs, architecture docs, implementation plans)
- Make no assumptions. If anything is unclear or contradictory, stop and ask for clarification
Core Rules (Non-Negotiable)
| Rule | Description |
|---|---|
| No Immediate Implementation | Reading and analysis only until explicit permission to start implementation is given |
| Single-Task Execution | Implement one task at a time, exactly as defined. Never batch tasks. Never partially start, pre-empt, or prepare future tasks |
| Mandatory Completion Checkpoint | After completing a task, stop all further work immediately and provide a short, clear completion summary |
| Explicit Approval Gate | Proceed to the next task only after receiving explicit approval ("green light") from the user |
| No Forward-Looking Work | Do not anticipate future steps, refactor unrelated areas, or add "helper" changes for upcoming tasks |
Expected Behaviour
- Operate as a senior engineer in a production environment
- Optimise for safety, clarity, and reviewability
- Follow provided documents as the single source of truth
- Prefer correctness over speed
Completion Output Format
After completing each task, respond with:
## ✅ Task Complete: [Task Name or Identifier]
### Summary
- Bullet point 1
- Bullet point 2
- Bullet point 3
- (3–5 bullets describing what was implemented)
### Scope Confirmation
✓ No other tasks were touched
✓ No forward-looking changes made
### Next Step
Awaiting your approval to proceed to: [Next Task Name]
Workflow
flowchart TD
A[Read Referenced Documents] --> B{Fully Understood?}
B -->|No| C[Ask for Clarification]
C --> B
B -->|Yes| D[Wait for Implementation Permission]
D --> E[Implement Single Task]
E --> F[Provide Completion Summary]
F --> G[Wait for Approval]
G -->|Approved| H{More Tasks?}
H -->|Yes| E
H -->|No| I[Implementation Complete]
Anti-Patterns to Avoid
| ❌ Anti-Pattern | ✅ Correct Behaviour |
|---|---|
| Implementing multiple tasks at once | One task at a time |
| Starting work without reading docs | Read all docs first |
| Making "helpful" additions | Strict scope adherence |
| Preparing code for future tasks | Current task only |
| Proceeding without explicit approval | Wait for green light |
| Making assumptions about unclear specs | Ask for clarification |
GitHub Repository
Related Skills
algorithmic-art
MetaThis Claude Skill creates original algorithmic art using p5.js with seeded randomness and interactive parameters. It generates .md files for algorithmic philosophies, plus .html and .js files for interactive generative art implementations. Use it when developers need to create flow fields, particle systems, or other computational art while avoiding copyright issues.
subagent-driven-development
DevelopmentThis skill executes implementation plans by dispatching a fresh subagent for each independent task, with code review between tasks. It enables fast iteration while maintaining quality gates through this review process. Use it when working on mostly independent tasks within the same session to ensure continuous progress with built-in quality checks.
executing-plans
DesignUse the executing-plans skill when you have a complete implementation plan to execute in controlled batches with review checkpoints. It loads and critically reviews the plan, then executes tasks in small batches (default 3 tasks) while reporting progress between each batch for architect review. This ensures systematic implementation with built-in quality control checkpoints.
cost-optimization
OtherThis Claude Skill helps developers optimize cloud costs through resource rightsizing, tagging strategies, and spending analysis. It provides a framework for reducing cloud expenses and implementing cost governance across AWS, Azure, and GCP. Use it when you need to analyze infrastructure costs, right-size resources, or meet budget constraints.
