What I do

• Continue execution from an existing plan in context/plans/.
• Read the selected plan and identify the next task from the first unchecked checkbox.
• Ask focused questions for anything not clear enough to execute safely.

How to run this

• Use this skill when the user asks to continue a plan or pick the next task.
• If context/ is missing, ask once: "context/ is missing. Bootstrap SCE baseline now?"
  • If yes, create baseline with sce-bootstrap-context and continue.
  • If no, stop and explain SCE workflows require context/.
• Read context/context-map.md, context/overview.md, and context/glossary.md before broad exploration.
• Resolve plan target:
  • If plan path argument exists, use it.
  • If multiple plans exist and no explicit path is provided, ask user to choose.
• Collect:
  • completed tasks
  • next task
  • blockers, ambiguity, and missing acceptance criteria
• Prompt user to resolve unclear points before implementation.
• Confirm scope explicitly for this session: one task by default unless user requests multi-task execution.

Plan file format

SCE plans are Markdown files stored in context/plans/. Tasks are tracked as checkboxes:

# Plan: Add user authentication

## Tasks
- [x] Scaffold auth module
- [x] Add password hashing utility
- [ ] Implement login endpoint        <- next task (first unchecked)
- [ ] Write integration tests
- [ ] Update context/current-state.md

The first unchecked - [ ] item is the next task to review and prepare.

Rules

• Do not auto-mark tasks complete during review.
• Keep continuation state in the plan markdown itself.
• Treat context/plans/ as active execution artifacts; completed plans are disposable and not a durable context source.
• If durable history is needed, record it in current-state context files and/or context/decisions/ instead of completed plan files.
• Keep implementation blocked until decision alignment on unclear points.
• If plan context is stale or partial, continue with code truth and flag context updates.

Expected output

Produce a structured readiness summary after review:

## Plan Review - [plan filename]

**Completed tasks:** 2 of 5
**Next task:** Implement login endpoint

**Acceptance criteria:**
- POST /auth/login returns JWT on success
- Returns 401 on invalid credentials

**Issues found:**
- Blocker: JWT secret source not specified (env var? config file?)
- Ambiguity: Should failed attempts be rate-limited in this task or a later one?

**ready_for_implementation: no**

**Required decisions before proceeding:**
1. Confirm JWT secret source
2. Confirm rate-limiting scope

When all issues are resolved:

**ready_for_implementation: yes**
Proceeding with: Implement login endpoint

• Explicit readiness verdict: ready_for_implementation: yes|no.
• If not ready, explicit issue categories: blockers, ambiguity, missing acceptance criteria.
• Explicit user-aligned decisions needed to proceed to implementation.
• Explicit user confirmation request that the task is ready for implementation when unresolved issues remain.

Related skills

• sce-bootstrap-context - creates the context/ baseline required by this skill