A scoped playbook, milestone table, role-capacity comparison, controlling dependency chain, risk register, and decision requests; an evidence-based status draft when prior status is supplied.
Dates and owners stay proposed where unconfirmed; it does not create tasks in project software. This is a self-directed Markdown skill, not an installed integration or hosted service.
These orientation steps are public. The paid instructions and files stay in your purchase download.
Download → Prepare → Draft → Review
01
Find and open your files.
Open the order-confirmation email and choose Access Downloads or View Order. Verify access using the code sent to your checkout email. Save the ZIP, extract a copy, and keep the entire skill folder together.
Package:StratBuild-Project-Delivery-Planner-v0.3.1.zip (v0.3.1). If the file is missing or your purchased version differs, contact support; do not purchase it again.
stratbuild-project-delivery-planner/① README.md — quickstart② SKILL.md — paid instructionsEXAMPLE.md — fictional worked exampleSTRATBUILD-LICENSE.txt — original license
These are filenames inside your purchase, not public download links. A .md file is a plain-text document; open it in a text editor or Markdown viewer.
02
Prepare one bounded task.
Read README.md and the license first. Supply the text of the purchased SKILL.md as task instructions using your assistant’s supported text or file mechanism. Label your source facts separately. If the host has context limits, use a smaller task and verify what it can read.
No automatic installation or connection.
This is a Markdown resource package. Native host installation and compatibility are not certified. Your AI account, privacy settings and any tool fees are separate. Only supply inputs you are authorized to use.
Bring the facts that matter.
Desired outcome, inspectable acceptance checks, and explicit exclusions.
Desired versus committed dates and the applicable business-day calendar.
Role availability, effort estimates or ranges, and existing commitments.
Dependencies, review turnaround, decision authority, and verified status evidence.
03
Try a small fictional example.
After loading your purchased instructions, use a brief like this. It is an orientation example, not a replacement for the paid workflow.
After loading the purchased SKILL.md instructions, help me create one small review draft for a fictional business. The desired result is: A scoped playbook, milestone table, role-capacity comparison, controlling dependency chain, risk register, and decision requests; an evidence-based status draft when prior status is supplied. Ask for missing source inputs. Keep unknown facts, amounts and permissions unresolved. Do not connect services, send messages or publish anything.
Illustrative walkthrough only
Prepare the inputs
Desired outcome, inspectable acceptance checks, and explicit exclusions.
Create a bounded draft
A scoped playbook, milestone table, role-capacity comparison, controlling dependency chain, risk register, and decision requests; an evidence-based status draft when prior status is supplied.
Review before use
The project owner confirms availability, named owners, reviewer response time, dependency readiness, acceptance authority, and any external commitments before execution.
Read EXAMPLE.md inside your purchase for the complete authored demonstration. Fictional examples and author rehearsals are not independent tests or customer results.
04
Review before using the draft.
The project owner confirms availability, named owners, reviewer response time, dependency readiness, acceptance authority, and any external commitments before execution.
Unprovided facts, amounts and permissions stay unresolved.
No external service is connected and no message, payment or publication occurs.
Keep source facts, missing decisions and human approval visible. Drafting does not authorize sending, spending, publishing or connecting a live system.
