finish-flow

Expand parent closing tasks into discrete verifiable sub-tasks with TaskCreate and status updates.

10|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/cookys/autopilot --skill finish-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finish-flow
Source: https://github.com/cookys/autopilot/tree/main/skills/finish-flow
Command: npx skills add https://github.com/cookys/autopilot --skill finish-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that the closing phase of a dev-flow is explicit and verifiable by expanding a single parent closing task into discrete subtasks, preventing steps from being skipped.

Core Features & Use Cases

  • Expands the parent closing task (e.g., L-5 or H-9) into size-specific sub-tasks, each with its own verification.
  • Enforces sequential execution and mandatory evidence collection via TaskCreate and status updates.
  • Supports L-size, H-size, Fix, and S-session endings; integrates with quality-pipeline for gating and with project lifecycle tooling for archival.

Quick Start

Invoke autopilot:finish-flow to break the current closing task into size-appropriate sub-tasks and begin executing them in order.

Frequently Asked Questions about finish-flow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate project closing tasks with verifiable sub-tasks?

Automate project closing tasks by expanding a single parent closing task into discrete, sequentially executed sub-tasks. This ensures each step generates concrete evidence outputs, preventing steps from being skipped during the development flow.

What is the best way to enforce sequential execution for dev-flow closing tasks?

Enforce sequential execution for dev-flow closing tasks by applying size-specific expansions to the parent task. Using TaskCreate and status updates mandates ordered completion and requires explicit sub-task subjects and descriptions for tracking.

Can I use size-aware task expansion for both L-size and H-size project endings?

Size-aware task expansion supports L-size, H-size, Fix, and S-session project endings. It breaks down the corresponding parent closing task, such as L-5 or H-9, into appropriate discrete sub-tasks with individual verification.

Does the project closing automation integrate with quality-pipeline gating?

Project closing automation integrates with quality-pipeline gating and project lifecycle tooling. This combination ensures that the expanded sub-tasks meet quality checks before archival and finalizes the closing phase with verifiable evidence.

Why do I need explicit subjects and descriptions for closing sub-tasks?

Explicit subjects and descriptions for closing sub-tasks are required to prevent ambiguity and skipped steps. This mandatory reporting ensures that the automated expansion of the parent task produces concrete, verifiable evidence outputs.

What are the limitations of automating dev-flow project closing?

A limitation of automating dev-flow project closing is its restriction to specific task sizes like L-size, H-size, Fix, and S-session. It requires a pre-existing parent closing task and cannot generate sub-tasks without explicit subjects and descriptions.