Skip to content
Back to skills

Danthamanvoiss Service Expansion Planner

ASecurity

Plan evidence-gated service expansion opportunities with assumptions, dependencies, and validation gates.

  • 76 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 22, 2026
businessrails

Works with

  • cli

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned September 22, 2026

npx -y skills add jiayaoqijia/cryptoskill --skill danthamanvoiss-service-expansion-planner --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Danthamanvoiss Service Expansion Planner?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Danthamanvoiss Service Expansion Planner
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jiayaoqijia-danthamanvoiss-service-expansion-planner/badge)](https://www.skillsdirectory.com/skills/jiayaoqijia-danthamanvoiss-service-expansion-planner)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: service-expansion-planner
description: Plan evidence-gated service expansion opportunities with assumptions, dependencies, and validation gates.
version: 0.1.0
tags: [client-success, expansion, planning, evidence-gates]
---

## Purpose

Plan evidence-gated service expansion opportunities with assumptions, dependencies, and validation gates.

## Use when

- Exploring additional service lines for an existing account.
- You need expansion hypotheses validated before any claim of readiness or ROI.

## Required inputs

- Current service scope, outcomes, and account priorities [client-provided].
- Capacity/fit constraints from context/BRAND-CONTEXT.template.md and context/CLIENT-CONTEXT.template.md.
- Stakeholder appetite, budget guardrails, and known risks.

## Safety/authority

- No expansion recommendation without explicit evidence gates.
- No invented ROI, timeline, or approval assumptions.
- Output remains proposal planning draft until stakeholder validation.

## Workflow

1. Identify expansion hypotheses tied to observed account needs.
2. Define evidence gates (data required, owner, pass/fail criteria) for each hypothesis.
3. Draft sequencing, dependencies, and risk mitigations.
4. Recommend next validation steps before commercial discussion.

## Output format
```

- Expansion hypothesis map
- Evidence gate table (hypothesis | required evidence | gate criteria | status)
- Sequenced validation plan
- Risks/dependencies and stakeholder questions
```

## Quality checks

- Each expansion idea has explicit evidence gate criteria before recommendation.
- No claim of expansion fit is made without cited supplied evidence.

## Related skills

retention-and-upsell-review, churn-risk-early-warning, crm-workflow-blueprint

Files in this skill

  • LICENSE1 KB
  • SKILL.md1.7 KB
  • SOURCE.md432 B
  • TRUST.auto.yaml2.2 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…