Run any Skill in Manus with one click

workplan-builder

Stars2

Forks0

UpdatedJuly 1, 2026 at 11:57

This skill should be used when the user asks to "turn this into a workplan," "build a hypothesis-driven workplan," "who's doing what on this analysis," or has a hypothesis tree (from this plugin or elsewhere) that needs owners, timelines, and data sources attached.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

daddia

daddia/claude-for-strategy

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

SKILL.md

readonly

name	workplan-builder
description	This skill should be used when the user asks to "turn this into a workplan," "build a hypothesis-driven workplan," "who's doing what on this analysis," or has a hypothesis tree (from this plugin or elsewhere) that needs owners, timelines, and data sources attached.
allowed-tools	Read, Grep, Glob
metadata	{"version":"0.3.0","owner":"consulting practice","review_cadence":"quarterly","work_shape":"structured-aggregation","permission_tier":"advisory","output_class":"draft-for-review","sourcing_policy":"volatile-facts-must-be-sourced"}

Workplan Builder

When to use

Translate hypothesis tree into executable workplan with owners, timelines, data sources, pre-stated so-whats.

What this skill does not do

Does not build hypothesis tree — route to hypothesis-tree if missing.
Does not assign owners without confirmation — flag TBD.
Does not invent data sources — flag unknown.

Preconditions

Input	If missing
Hypothesis tree	Ask to run `hypothesis-tree` or supply structure
Owner/timeline constraints	Ask; no arbitrary day counts

Provisional mode

Missing owners/timelines: table with TBD flags; no silent placeholders.

Trust spine

Confidence bands (structured-aggregation): High = all rows complete; Medium = some TBD; Low = tree missing branches.
Escalation: Disproportionate effort vs so-what → flag revisit tree.

Workflow

Get hypothesis tree.
Per sub-hypothesis: analysis method, data source, owner, timeline, expected so-what (from tree).
Sanity-check effort vs payoff.
Output table; flag incomplete rows.

Output format

Hypothesis	Analysis	Data source	Owner	Timeline	Expected so-what
...	...	...	...	...	...

Flags: effort/payoff mismatches; missing owner/timeline/source.

Worked example

Input: Tree branch "elasticity >15% in mid-tier."

Row: Cohort price-volume analysis | billing warehouse | TBD owner | before steering 3/15 | if true, supports revert recommendation.

Quality checks before delivering

So-what carried from tree pre-analysis
No invented sources or owners
Effort flags applied

Propose profile update

When a stable convention surfaces during this run (thresholds, naming, tone, output format, or recurring corrections), propose a profile update: show the exact diff against ~/.claude/plugins/config/claude-for-strategy/consulting/CLAUDE.md (org-wide facts go to org-profile.md), ask for confirmation, and write only on yes. Only /consulting:practice-setup auto-applies a full profile write.

Outputs

Follows plugin CLAUDE.md § Outputs. Next: drop into tracker or steering deck.

More from this repository

same repository

auto-updater

daddia/claude-for-strategy

Check installed community skills for updates. Shows a diff and requires explicit approval before applying. Use when the user says "check for updates", "update my skills", "anything new for my installed skills", or when invoked from the registry-sync agent.

2026-07-012

practice-setup

daddia/claude-for-strategy

Engagement-profile interview that recommends and installs a starter pack of community strategy skills. This IS the practice setup for the whole ecosystem — it asks what kind of strategist you are and recommends what to install first. Use on fresh install, when the user says "get me started" or "what should I install", or to re-run the integration-availability check after adding or removing an MCP connector.

2026-07-012

skill-installer

daddia/claude-for-strategy

Install a community skill from a watched registry. Reads the allowlist first, fetches, shows the RAW SKILL.md (not just a summary), runs structural trust checks, runs skills-qa, and only writes files after explicit user approval. Use when the user says "install [skill]", picks install from browse, or provides a direct skill URL.

2026-07-012

skills-qa

daddia/claude-for-strategy

Evaluate a skill against the Strategy Skill Design Framework — thirteen design parameters (including trust-surface, freshness, schema validation, and conflict detection), three strategy-specific failure modes, and a three-band verdict (Ready / Some Concern / Material Concerns). Use when deciding whether to trust a community skill before installing it, before deploying a first-party skill to your team, or whenever the user asks "should I trust this?" or "is this skill well-designed?". Runs automatically as part of /strategy-builder-hub:skill-installer.

2026-07-012

allocate-resources

daddia/claude-for-strategy

This skill should be used when the user asks to "review our resource allocation," "are we funding the right things," "build a portfolio allocation view," or needs current spend, headcount, or management attention checked against strategic priority for misallocation.

2026-07-012

synergy-stress-test

daddia/claude-for-strategy

This skill should be used when the user asks to "stress-test these synergies," "is this deal's synergy case realistic," or has a deal or partnership's projected synergies that need cost/revenue separation, evidence checks, and a base-rate haircut.

2026-07-012

name	workplan-builder
description	This skill should be used when the user asks to "turn this into a workplan," "build a hypothesis-driven workplan," "who's doing what on this analysis," or has a hypothesis tree (from this plugin or elsewhere) that needs owners, timelines, and data sources attached.
allowed-tools	Read, Grep, Glob
metadata	{"version":"0.3.0","owner":"consulting practice","review_cadence":"quarterly","work_shape":"structured-aggregation","permission_tier":"advisory","output_class":"draft-for-review","sourcing_policy":"volatile-facts-must-be-sourced"}

Workplan Builder

When to use

Translate hypothesis tree into executable workplan with owners, timelines, data sources, pre-stated so-whats.

What this skill does not do

Does not build hypothesis tree — route to hypothesis-tree if missing.
Does not assign owners without confirmation — flag TBD.
Does not invent data sources — flag unknown.

Preconditions

Input	If missing
Hypothesis tree	Ask to run `hypothesis-tree` or supply structure
Owner/timeline constraints	Ask; no arbitrary day counts

Provisional mode

Missing owners/timelines: table with TBD flags; no silent placeholders.

Trust spine

Confidence bands (structured-aggregation): High = all rows complete; Medium = some TBD; Low = tree missing branches.
Escalation: Disproportionate effort vs so-what → flag revisit tree.

Workflow

Get hypothesis tree.
Per sub-hypothesis: analysis method, data source, owner, timeline, expected so-what (from tree).
Sanity-check effort vs payoff.
Output table; flag incomplete rows.

Output format

Hypothesis	Analysis	Data source	Owner	Timeline	Expected so-what
...	...	...	...	...	...

Flags: effort/payoff mismatches; missing owner/timeline/source.

Worked example

Input: Tree branch "elasticity >15% in mid-tier."

Row: Cohort price-volume analysis | billing warehouse | TBD owner | before steering 3/15 | if true, supports revert recommendation.

Quality checks before delivering

So-what carried from tree pre-analysis
No invented sources or owners
Effort flags applied

Propose profile update

Outputs

Follows plugin CLAUDE.md § Outputs. Next: drop into tracker or steering deck.