Skip to content
Back to skills

Controlled Implementation

ASecurity

Execute implementation work in a strictly controlled manner.

  • 666 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added February 8, 2026
documentationgo

Security analysis

A100/100

Scanned February 10, 2026

npx -y skills add majiayu000/claude-skill-registry --skill controlled-implementation --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Controlled Implementation?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Controlled Implementation
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-controlled-implementation/badge)](https://www.skillsdirectory.com/skills/majiayu000-controlled-implementation)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: controlled-implementation
description: Execute implementation work in a strictly controlled manner.
---

# 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**:

1. Read and fully understand **all** referenced documents provided by the user (design specs, architecture docs, implementation plans)
2. 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:

```markdown
## ✅ 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

```mermaid
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 |

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.