One-Phase Implementation With Approval Gates
Implement one reviewable phase, verify its scope, and stop for explicit approval before committing or advancing.
Before & after
Same prompt, same agent — the only difference is the skill.
I'll build a complete authentication system for your app. Let me break this into phases: Phase 1 is database schema for users and sessions. Phase 2 is login/signup endpoints. Phase 3 is JWT token generation and refresh logic. Phase 4 is frontend forms (login, signup, password reset). Phase 5 is password reset email flow. Phase 6 is two-factor authentication. Let me start building everything now... [After 4 hours of work, returns 8,000-line diff implementing all 6 phases without any pause for review or approval.]
PHASED IMPLEMENTATION: AUTHENTICATION SYSTEM Planned phases: → Phase 1: Database schema → Phase 2: Login/signup endpoints → Phase 3: JWT + refresh logic → Phase 4: Frontend forms → Phase 5: Password reset → Phase 6: 2FA ===== PHASE 1: DATABASE SCHEMA ===== Files to create/modify: prisma/schema.prisma • User model: id, email (unique), passwordHash, emailVerified, createdAt, updatedAt • Session model: id, userId (FK), token (hashed), expiresAt, createdAt • PasswordReset model: id, userId (FK), token (hashed), expiresAt Migration: → Command: npx prisma migrate dev --name add_auth_schema → Generates migration, applies to local DB Changes summary: • 3 new tables (User, Session, PasswordReset) • 4 indexes (email unique, session userId, passwordReset userId, token expiry) • No API endpoints yet Test: DB schema applies without error ===== HALT: AWAITING APPROVAL ===== I have completed Phase 1. Before proceeding to Phase 2 (endpoints), I need your explicit approval: Checklist to verify: [ ] You reviewed the schema and agree with table structure [ ] You're happy with password hashing approach (bcrypt cost 12) [ ] You confirmed: Session expiry = 7 days, PasswordReset expiry = 1 hour If approved: Reply with looks good, proceed If changes needed: → Change Session expiry to 30 days → I'll update the schema and wait for re-approval before Phase 2 ===== WHAT PHASE 2 WILL BUILD (preview only) ===== Not building yet—just showing what's next: • POST /auth/signup endpoint (create user, hash password, send verification email) • POST /auth/login endpoint (check password, create session) • POST /auth/logout endpoint (delete session) Files: Create app/api/auth/signup.ts, app/api/auth/login.ts ===== AWAITING YOUR GO-AHEAD ===== Once you approve Phase 1, I'll implement Phase 2, commit it, and halt again for your review.
About this skill
“I asked for phase one, and it implemented the whole plan.” This workflow keeps implementation inside one agreed phase and ends with a concrete review handoff. Passing tests, convenient refactors, and unfinished later phases never become permission to keep coding.
What it does
- Identifies the next authorized phase from the plan, implementation evidence, and previous approvals.
- Defines the phase's acceptance criteria, allowed changes, and excluded later work before editing.
- Keeps necessary supporting changes separate from unrelated cleanup and future functionality.
- Checks the final diff against the starting state and reports validation results honestly.
- Stops for explicit review approval, with separate handling for committing and starting the next phase.
- Preserves the current checkpoint across revisions, interruptions, and resumed sessions.
What you get
One implemented phase with a focused change summary, acceptance-check results, review instructions, and an explicit approval checkpoint. If the phase cannot be completed within its agreed boundary, you get the specific blocker and a proposed scope adjustment before further implementation.
Best for
Developers and technical leads implementing an existing phased plan who want small diffs, human review between phases, and predictable control over commits and subsequent work.
SKILL.md preview
---
name: one-phase-implementation-with-approval-gates
description: Execute one phase of an existing implementation plan, verify its acceptance criteria and diff boundaries, then stop for explicit approval before committing or advancing. Use when the user says "implement phase one", "continue the phased plan", "do only the next phase", "stop after each phase", "my coding agent keeps implementing the whole plan", "wait for my review before committing", or "resume from the last approved phase".
---
# One-Phase Implementation With Approval Gates
… (sign up to view the full skill)More development skills
View all Development skills →Performance Bottleneck Profiling: Node, Python, Go
Classifies a slowdown, gives exact profiler commands, reads the output, and proves the fix with same-conditions p95/p99 numbers.
Feature Scaffolding with Working Tests
Turn a short feature spec into code, runnable tests, and integration wiring that match your existing project.
Feature Flag Rollouts and Kill Switches
Design staged flag rollouts, verify rollback paths, and audit flag debt with explicit defaults, gates, and retirement plans.
Microcontroller Firmware and RTOS Engineering
Build and debug MCU firmware with bounded ISR/RTOS timing, safe DMA ownership, and measured power budgets.