Strategic Task Planning & Delivery Reconciliation
New: reconcile strategic goals with project delivery
Uses stable objectives, work packages and evidence by dimension to coordinate parallel delivery while retaining business acceptance gaps.
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.
Guide
The guide has not been uploaded yet. Once available, you can view it online or download it.
Not uploaded
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
- 01
Separate decisions from proposals, assumptions and withdrawn items
- 02
Define observable deliverables and safe parallel boundaries
- 03
Integrate on a shared baseline and recheck affected paths
- 04
Report gaps against objectives, conditions and evidence
Getting started
Download and extract the complete ZIP, then read its README. 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.