Skip to content
Skills Library
Management & product · Planning

phase-spec-execution

/phase-spec-execution

Execute large tasks through explicit phases with acceptance criteria, required commands, and state updates. Use when work is too large for one implementation pass but too important to leave as a vague checklist. Keep phases falsifiable, end-to-end, and small enough that each one can be verified honestly before moving on.

Licence
MIT
Last repository change
14.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 14.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Execute large tasks through explicit phases with acceptance criteria, required commands, and state updates. Use when work is too large for one implementation pass but too important to leave as a vague checklist. Keep phases falsifiable, end-to-end, and small enough that each one can be verified honestly before moving on.

Original author description

Execute large tasks through explicit phases with acceptance criteria, required commands, and state updates. Use when work is too large for one implementation pass but too important to leave as a vague checklist. Keep phases falsifiable, end-to-end, and small enough that each one can be verified honestly before moving on.

How it works

  1. Use When
  2. Core Rules
  3. Phase Template
  4. Workflow
  5. State Discipline
  6. Anti-Patterns
  7. Final Report
Original SKILL.md headings · 63 lines, 310 words
SKILL.md preview
---
name: phase-spec-execution
description: Execute large tasks through explicit phases with acceptance criteria, required commands, and state updates. Use when work is too large for one implementation pass but too important to leave as a vague checklist. Keep phases falsifiable, end-to-end, and small enough that each one can be verified honestly before moving on.
license: MIT
metadata:
  abvx_status: experimental
  abvx_origin: adapted
---

# Phase Spec Execution

Turn a large task into a sequence of falsifiable execution slices instead of one broad blob of work.

## Use When

- the task spans multiple files, layers, or user-visible milestones;
- there is real sequencing or dependency ordering;
- you need clearer state than "still working";
- the user wants autonomy without losing verification discipline.

## Core Rules

- Slice vertically where possible. Each phase should move observable behavior.
- Give every phase explicit acceptance criteria.
- Attach the narrowest mandatory commands that can prove the phase.
- Update state after each phase so the next pass does not rediscover context.
- Do not create more phases than the task needs.

## Phase Template

For each phase, define:

- objective;
- dependencies or prerequisites;
- files or surfaces likely to change;
- acceptance criteria;
- mandatory verification commands;
- known risks;
- handoff note if the phase cannot complete.

## Workflow

1. Identify the end state the user actually wants.
2. Break the work into the smallest useful number of ordered phases.
3. Write or state one clear objective per phase.
4. Before implementing a phase, restate its acceptance criteria.
5. Execute only the current phase.
6. Run the phase verification commands.
7. Record what changed, what passed, and what remains.
8. Only then advance to the next phase.

## State Discipline

Track at least:

- current phase;
- completed phases;
- failed checks and why;
- assumptions that changed;
- open risks for the next phase.

## Anti-Patterns

- Do not create "phase 1: backend, phase 2: frontend, phase 3: tests" by default.
- Do not advance on "looks good" when acceptance criteria are falsifiable.
- Do not let plan files become larger than the implementation itself.

## Final Report

Report completed phases, skipped phases, criteria met, criteria deferred, and any remaining integration risk.
Files in this package (3)
  • SKILL.md 2 KB
  • SKILL_CARD.md 1 KB
  • agents/openai.yaml 1 KB

Versions

The database has no other skills named phase-spec-execution.

Database snapshot: 13.11.2026 · package version cbb42329f892 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100write-phase-plan
    Writes or restructures an implementation plan in the format the phase-orchestrator skill consumes: dependency-ordered phases with explicit scope, acceptance criteria, validation commands, and status/log conventions. Use when the user asks to write a plan for phase orchestration,…
  • 100write-phase-plan
    Writes or restructures an implementation plan in the format the phase-orchestrator skill consumes: dependency-ordered phases with explicit scope, acceptance criteria, validation commands, and status/log conventions. Use when the user asks to write a plan for phase orchestration,…
  • 100prd-to-plan
    Turns a product requirements document into a phased implementation plan saved as a Markdown file in the repository: a requirement ledger, the decisions every phase depends on, and an ordered list of phases that each end in something demonstrable, with checks and verification…
  • 100phase-review
    Review implementation plans from the .tasks/ directory for flaws before committing — either a single phase (phase mode) or across all phases of a task for consistency (cross-phase analyze mode). Triggers on: 'use phase mode', 'review phase', 'review the plan', 'check phase',…
  • 90implementation-plan
    Convert a plan, PRD, backlog item, or vague feature into ordered implementation work with acceptance criteria and verification. Use when the user asks to break down work, make an implementation plan, create tasks, plan execution, or use slice-plan.
  • 90write-spec
    Write a feature design spec with numbered acceptance criteria before any plan or code. Use when starting any feature, or when a request is too vague to build without guessing.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.