execute-phase

A phase-based implementation runner for a planned feature or bug fix. A phase is one defined part of a larger engineering plan with its own checks.

In plain words
What is it for?
It executes all remaining phases or one explicitly selected phase, runs phase-local quality gates, creates commits, and completes the pull-request workflow.
Why use it?
It prevents unfinished plan phases from being skipped and ties each phase to acceptance checks, commits, recovery steps, and final close-out.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/gtrabanco/agentic-workflow/execute-phase
Any agent
npx skills add gtrabanco/agentic-workflow --skill execute-phase
Clone the repo
git clone --depth 1 https://github.com/gtrabanco/agentic-workflow

Made for: Claude Code, Codex.

Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,584 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00054 $0.01584
Opus 5 $0.00027 $0.00792
Sonnet 5 $0.00011 $0.00317
Haiku 4.5 $0.00005 $0.00158

Measured 2d ago against content hash 37119f8175f4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

execute-phase scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

packages/pi-agentic-workflow/skills/execute-phase/SKILL.md · 116 lines

How it starts

The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Execute Phase

Modes: unit loop (default when P<n> is omitted) executes every remaining phase through close-out, with one gate/commit per phase; explicit phase P<n> executes exactly that phase; legacy SPECs without ## Phases run once. --fix selects a fix unit.

First matching row wins:

Invocation shape Queue
target + explicit P<n> only the literal P<n> argument; ignore other unfinished phases
target, no phase only the literal unfinished phase IDs found in the ledger, in order
legacy SPEC without phases one legacy pass

Never infer a phase ID absent from the invocation/ledger.

Turn contract

Load and verify the canonical Turn contract (11 boxes) before ending every turn. Skill-specific additions and push policy live only in PREFLIGHT.md. Missing reference → STOP.

Hard rules

  • Honor Workflow conventions (branch/PR, gate-before-commit, docs language). Run git branch --show-current before editing/committing; if main, create the working branch first (unless the user explicitly uses main).
  • Phases are P1, P2, …. The <phase> argument and every reference in PLAN.md/TASKS.md/progress.md/commits is P1, P2, … ("phase N") — never S1/S2/"Step N". If a plan you're handed uses S1-style labels, normalize it to P1, … before executing and note it in decisions.md.
  • Implement only the requested scope: all remaining ledger phases when omitted, or exactly P<n>. Never invent/bundle across phase boundaries; unit-loop mode still gates and commits each phase.
  • Stop after the gate passes; keep commits small and reviewable.
  • Feature mode: update TASKS.md, progress.md, testing.md, known-issues.md each phase (and decisions.md if architecture moved).
  • Plan conflict: update TASKS.md/PLAN.md and record why in decisions.md; never silently diverge.
  • Dependency gate before any work — the preflight resource owns it. No edit, branch, or commit for an unmerged dependency closure unless the user passed --force.
  • Phase-lint before any edit — the preflight resource runs it after dependency/own-status gates. Any FAIL stops unless the user passed --force.

Read the full file on GitHub · 116 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 116 lines · 54 tokens per session scan A 37119f8175f4

Subscribe to this mod's changes

execute-phase is a skill published in the GitHub repository gtrabanco/agentic-workflow (20 stars, last pushed 2d ago), licensed MIT. It adds 54 tokens to every session and 1,584 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

think-like-me

Personal engineering rules and reasoning patterns the user has curated over time. Consult BEFORE writing, modifying, debugging, or designing any technical feature — rules often cover domain-specific gotchas (e.g., mobile audio timers need background mode) that generic answers miss. Also triggers on /learn-this, "learn…

kakha13/think-like-me · 88 tokens

workers-best-practices

Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from…

cloudflare/skills · 72 tokens

find-journalists

Build, refine, dedupe, and enrich small fit-checked journalist lists for newsjack campaigns. Uses the newsjack CLI (preferred) or the medialyst MCP for news search and journalist enrichment, and falls back to a best-effort local mode with no verified contacts; the agent owns how returned data is organized.

elvisun/newsjack · 69 tokens

story-origin-check

Recover the first public timestamp and canonical major coverage for a newsjacking signal, then decide whether newer coverage is the same story, a different story, or a materially new development.

elvisun/newsjack · 40 tokens

annotating-task-lineage

Annotate Airflow tasks with data lineage using inlets and outlets. Use when the user wants to add lineage metadata to tasks, specify input/output datasets, or enable lineage tracking for operators without built-in OpenLineage extraction.

astronomer/agents · 51 tokens

relevance-coarse-filter

Cheap, high-recall first-pass filter that removes obvious junk from a detector candidate pool before expensive story-origin research and PR judgment. Decides keep, monitoronly, or reject — never ranks, writes angles, verifies dates, or decides whether to pitch.

elvisun/newsjack · 57 tokens