Hundred-Day Plan
The first hundred days as a bandwidth-budgeted, dependency-sequenced plan with week-one reporting and a published cut list, built to be executed.
- What
- The first hundred days as a bandwidth-budgeted, dependency-sequenced plan with week-one reporting and a published cut list, built to be executed.
- Cost
- Free
- Needs
- Use "Hundred-Day Plan" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
⚠️ **Finance warning / Avertissement finance** : informational only, not investment advice. A good first-hundred-days plan protects value, it does not create a guarantee: portfolio companies can still underperform or lose money, there is a real risk of loss, and no plan here is a promise of return. Curated by Skill Harbor: the hundred-day plan skill of the private equity pack in andreworia/claude-finance-skills. Use it between signing and completion, when the team converts the investment thesis into what actually happens after the wire clears; it applies equally to a carve-out carrying TSA obligations and to a bolt-on where the hundred days belong to integration, and it exists to fix the classic failure mode, a draft that already runs to thirty actions. The method budgets bandwidth before choosing any moves: count the executive-days genuinely available (executives who can carry change work, times fourteen weeks, times the share of their week not spent running the business, usually one day in five), and treat any plan costing more than that budget as a wish list. It then chooses three to five moves only, each of which must protect value acquired, unlock a named lever in the EBITDA bridge, or buy information diligence could not, prices each in executive-days and holds back about 20 percent because something unforecast always arrives in month one. The reporting cadence is installed in week one before any initiative (monthly close date, the pack, the board calendar, the weekly cash report and the covenant certificate cycle), completion-only work goes early (retention conversations, top-ten customer calls, bank and insurance handover, the authority matrix), and moves are sequenced on dependencies, not enthusiasm, so reporting precedes the data and the data precedes the pricing review that consumes it. Each move gets an owner, a success criterion and a stop condition, the observable that means it should be halted or deferred, and the plan publishes its cut list: what is deliberately not being done, why, and the date each item is reconsidered, because unpublished cuts return as informal asks and eat the contingency. It closes with a day-100 gate, not a celebration, marking each move landed, partly landed or not landed and reconciling days spent against budget. The worked example in the file, Thornbury Care Services, is fictional and illustrative. From the andreworia/claude-finance-skills repository (MIT). Honest caveats: the executive time commitments, TSA obligations and covenant dates are yours to supply realistically and to verify; a bandwidth budget built on optimistic availability produces exactly the wish list the skill warns against. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Hundred-Day Plan" with your Muse. Prerequisites: the investment thesis and EBITDA bridge from the IC memo, the org chart with realistic executive time commitments, the signing-to-completion timetable and any TSA obligations, day-one issues with their operational mitigants, and the credit agreement reporting and covenant test dates. No account and no credentials are involved: this skill produces a plan document only, and the time and obligation inputs are yours to state honestly and verify. Informational only, not investment advice. 1. Open the skill: https://github.com/andreworia/claude-finance-skills/blob/main/packs/private-equity/skills/hundred-day-plan/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Build the hundred-day plan: show the bandwidth budget in executive-days with its assumptions, choose three to five moves priced against it with owners, success criteria and stop conditions, install the week-one reporting cadence, sequence the moves on dependencies by fortnight, and publish the cut list with reconsideration dates and the day-100 gate format, all in prose." 3. Count the days yourself before accepting the plan: if the moves cost more than the budget minus contingency, the plan is a wish list and a move has to move to the cut list. Tip: protect the week-one cadence even when it feels like plumbing; everything else in the plan is measured through it. Safety: a skill is plain-text instructions; it runs nothing by itself. Planning and documents only, no orders and no account access. Informational only, not investment advice.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.