How do I install the Practice Setup skill?

Run npx skillmds@latest add daddia/practice-setup-8 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Practice Setup safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Practice Setup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Practice Setup free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Practice Setup?

daddia (@daddia) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Practice Setup by daddia — Agent Skill

Name: Practice Setup
Rating: 4.5 (2 reviews)
Author: daddia

Practice Setup

This skill should be used when the user runs "/value-realisation:practice-setup", asks to "set up the value-realisation plugin," "teach Claude how we track benefits," or wants to redo that setup after the benefits framework, governance model, or realisation cadence changes materially.

daddia Updated Sep 22, 2026

File contents

Practice Setup — value-realisation

When to use

Run before benefits skills produce tailored output. Baseline-discipline answer matters — get honest answer before anything else.

What this skill does not do

Does not map or track benefits — writes profile only.
Does not auto-write without confirmation.
Does not replace propose profile update — other skills must show diffs and ask before profile changes.

Preconditions

Offer quick vs full; read org profile via shared framework when applicable.

Provisional mode

Unanswered items → "no strong preference — will flag baselines and attribution conservatively by default."

Trust spine

Structured-aggregation bands; explicit confirmation; baseline discipline recorded honestly.

Shared framework

Read ../../references/practice-setup-framework.md with value-realisation as plugin name where org layer needed.

Plugin profile: ~/.claude/plugins/config/claude-for-strategy/value-realisation/CLAUDE.md

Plugin-specific interview

Benefits framework and taxonomy.
Governance — benefit owner vs delivery PM; escalation; decision log home.
Baseline discipline — before vs after go-live (push for honest answer).
Attribution convention.
Cadence — realisation window, tracking, review triggers.
Cross-plugin: transformation/corporate-strategy installed?
Seed documents (full mode).
Write profile per ../../CLAUDE.md template into the config path above.
Confirm and summarize.

Propose profile update: all other skills — org facts to org profile; benefits framework, baseline discipline, and cadence facts to plugin profile.

Output format

Summary of profile changes; files written on confirmation.

Worked example

Input: Baselines usually reconstructed after go-live; judgment-based attribution; quarterly tracking.

Summary excerpt: Baseline discipline recorded as post-go-live; downstream skills will flag RETROFITTED BASELINE conservatively.

Quality checks before delivering

Baseline discipline honest (not rounded up)
Benefit owner vs PM distinction captured
Confirmation before write

Outputs

Follows plugin CLAUDE.md § Outputs. Next: benefits-map or benefits-register.

---name: practice-setup-8description: This skill should be used when the user runs "/value-realisation:practice-setup", asks to "set up the value-realisation plugin," "teach Claude how we track benefits," or wants to redo that setup after the benefits framework, governance model, or realisation cadence changes materially.---# Practice Setup — value-realisation## When to useRun before benefits skills produce tailored output. Baseline-discipline answer matters — get honest answer before anything else.## What this skill does not do- **Does not map or track benefits** — writes profile only.- **Does not auto-write without confirmation.**- **Does not replace propose profile update** — other skills must show diffs and ask before profile changes.## PreconditionsOffer quick vs full; read org profile via shared framework when applicable.## Provisional modeUnanswered items → "no strong preference — will flag baselines and attribution conservatively by default."## Trust spineStructured-aggregation bands; explicit confirmation; baseline discipline recorded honestly.## Shared frameworkRead `../../references/practice-setup-framework.md` with `value-realisation` as plugin name where org layer needed.**Plugin profile:** `~/.claude/plugins/config/claude-for-strategy/value-realisation/CLAUDE.md`## Plugin-specific interview1. Benefits framework and taxonomy.2. Governance — benefit owner vs delivery PM; escalation; decision log home.3. Baseline discipline — before vs after go-live (push for honest answer).4. Attribution convention.5. Cadence — realisation window, tracking, review triggers.6. Cross-plugin: transformation/corporate-strategy installed?7. Seed documents (full mode).8. Write profile per `../../CLAUDE.md` template into the config path above.9. Confirm and summarize.**Propose profile update:** all other skills — org facts to org profile; benefits framework, baseline discipline, and cadence facts to plugin profile.## Output formatSummary of profile changes; files written on confirmation.## Worked example**Input:** Baselines usually reconstructed after go-live; judgment-based attribution; quarterly tracking.**Summary excerpt:** Baseline discipline recorded as post-go-live; downstream skills will flag RETROFITTED BASELINE conservatively.## Quality checks before delivering- [ ] Baseline discipline honest (not rounded up)- [ ] Benefit owner vs PM distinction captured- [ ] Confirmation before write## OutputsFollows plugin `CLAUDE.md` § Outputs. Next: `benefits-map` or `benefits-register`.

Frequently asked questions