Strategy & projects · SKILL

Strategic Task Planning & Delivery Reconciliation

Turn strategic records into verifiable work packages, coordinate dependencies and integration, and assess code, live operation and business results separately.

Skill introduction

When meeting decisions split into parallel work, project leads use the authorized decision, baseline and receipts to record work packages, dependencies, integration owners and gaps.

How to verify the work

Match deliverables and evidence against each objective. Check code, actual operation and business acceptance separately. Rerun affected integration paths and record the version and environment.

When to hand it over

Give team leads the common baseline and acceptance criteria. Route missing permissions, interface details or execution evidence to the responsible owner before proceeding.

What to measure

Track packages with acceptance evidence and issues left without an owner at closeout.

What it does

Turn strategic decisions into verifiable work packages, dependencies, parallel assignments and integration tasks.

What it helps with

Reconcile original objectives and check code, actual operation and business acceptance separately.

Why it matters

Keep scope and ownership visible across teams through delivery.

PDF · Chinese

Guide

Core guidance, examples and a revision worksheet. PDF in Chinese.

V1.1 · 13 pages · 232 KB

Usage guide

Recover goals, constraints and acceptance conditions from actual decisions, then trace project deliverables back to those goals. Independent work can proceed in parallel while business conditions still unmet after technical delivery remain visible.

What to prepare

  • Strategic records, meeting decisions, goals and success conditions
  • Project baselines, read/write boundaries, dependencies and authorized actions
  • Existing deliverables, versions, environments and acceptance evidence

What you receive

  • An objective and work-package ledger with dependencies and integration owners
  • Separate code, operational and business states with evidence gaps
  • Reconciliation results, blockers, next owners and change records

Who it is for

  • Implementing meeting decisions across projects and repositories
  • Integrating parallel AI work and reviewing a delivery phase

How the work progresses

  1. 01

    Separate decisions from proposals, assumptions and withdrawn items

  2. 02

    Define observable deliverables and safe parallel boundaries

  3. 03

    Integrate on a shared baseline and recheck affected paths

  4. 04

    Report gaps against objectives, conditions and evidence

  5. 05

    For handovers across conversations, record the latest decision, authorized actions, target version, automatic triggers and pending work.

Getting started

Download and extract the complete ZIP. Read the README if included, or start with SKILL.md. Install the complete folder containing SKILL.md in your AI tool’s skills directory under the skill name. In a multi-version repository, choose the version you need and retain its supporting files. Try a small task with the required inputs and review the result.

Scope and limits

  • Merged code, passing builds, production operation and business acceptance are distinct; governance actions are not closed automatically.
  • The offline checker neither authenticates evidence links nor changes task states, and grants no additional push, messaging or publication authority.
  • The source and fictional ledger are Chinese; seven-language descriptions do not imply fully translated packages.

Updates for this Skill

Back to My Skills All updates
SEARCH