---
name: pdn-business-planning
description: Prepare formal, reviewable business-planning drafts when the user asks for a business plan or structured planning artifact such as plan sections, KPIs, milestones, a roadmap, assumptions, risks, responsibilities, or execution materials. Reuse established context and preserve uncertainty; do not invent market validation, forecasts, or missing evidence.
license: CC BY-ND 4.0. See LICENSE.txt for complete terms.
---

# PDN-Planning v0.4.7

Turn established discussion into a useful planning draft for review or sharing with stakeholders, financial institutions, advisors, or specialists. The requested artifact may include business-plan sections, KPIs, milestones, roadmaps, assumptions, risks, responsibilities, decisions, and execution materials suited to the user's purpose.

## When to take responsibility

Take the lead when the user asks for a formal plan or structured planning output. A generic question about what to do next, future action, or business advice is not by itself a request for a formal planning artifact. When the user also requests structural diagnosis or detailed financial calculations, keep those contributions distinct and compose them by section where possible.

Do not take over PDN's first-principles structural/causal diagnosis merely because the output may later inform a plan. Do not claim accounting, tax, legal, or other professional authority.

## Prepare a reviewable draft

1. Identify the requested artifact, audience, time horizon, and level of detail when supplied.
2. Reuse established context, including **facts**, **hypotheses**, **assumptions**, **unknowns**, the **current objective**, and any **prior specialist output**. Preserve sources and status; do not silently restart, or turn prior draft recommendations into confirmed facts.
3. Distinguish confirmed facts, assumptions/hypotheses, unknowns, risks, decisions, responsibilities, and items needing external or expert confirmation where relevant.
4. Organize the requested material into a fit-for-purpose structure. Use placeholders, ranges grounded in user input, or explicit unknowns where evidence is absent.
5. Do not invent market validation, forecasts, financial inputs, customer evidence, or metrics to make the plan look complete. Clearly mark illustrative scenarios and proposed targets.
6. Keep financial arithmetic and accounting judgments within the information provided or route the explicit calculation portion to an appropriate specialist workflow where available. Do not make tax or legal determinations.
7. When delivering a substantive plan, add a concise status note such as “Draft for stakeholder review.” Avoid repetitive or alarmist disclaimers.

## Quality bar: useful as delivered

A draft is still expected to be good enough for its audience to read and act on. Placeholders mark missing evidence; they do not excuse weak structure or loose logic.

### Fit the structure to the audience and purpose

Choose emphasis from the purpose rather than a fixed template:

- internal investment decision or approval: the decision requested, options compared, rationale with its evidence status, and continue/stop criteria;
- lender or financial institution: business overview, revenue and cost drivers, use of funds, repayment basis, risks and mitigations, with figures only as supplied or clearly hypothetical;
- partner or stakeholder sharing: shared objective, roles and responsibilities, milestones, and what each party needs to decide;
- team execution: tasks, owners, sequence and dependencies, and review cadence.

If the audience is unknown and it would materially change the structure, ask once; otherwise state the assumed audience at the top.

### Keep the plan's logic traceable

Link issue → objective → intervention → causal hypothesis (why the intervention should move the outcome) → KPIs → milestones → decision gates. When a prior diagnosis exists, carry its causal hypothesis into the plan instead of restating generic goals. Use only the elements the requested artifact needs, except the required elements in the next subsection:

- KPIs: separate leading from lagging indicators; for each give definition, calculation, data source, frequency, owner, baseline (or "unknown"), and target with its status (proposed or agreed).
- Milestones: dated or sequenced, each with an observable completion criterion.
- Decision gates: for uncertain initiatives, stage the commitment and state which results mean continue, adjust, or stop.
- Assumption register: each key assumption with its basis, how much the plan depends on it, and how and by when it will be verified.
- Risks: early-warning sign, likely effect, response, and owner.

### Required elements that a form must not drop

When the plan contains an uncertain initiative or numeric targets, the separation of leading and lagging KPIs and the decision gates are required, even when the user asks for a specific form (for example a lender's or public institution's standard application form) that has no place for them. Keep the form's sections and order as requested, then add a clearly titled section after them (for example "KPIs and decision points"). Likewise, do not defer a section the audience needs, such as the repayment basis for a lender, until "conditions are fixed": show it as scenarios built from the supplied figures, and list the inputs still to be confirmed.

### Make it readable on its own

Start with a short summary: purpose, the key decision or ask, main figures as supplied, and the biggest uncertainty. State the status, date or as-of basis, and a legend separating confirmed facts, assumptions, and unknowns. Write placeholders as actionable requests, for example "[To confirm: monthly new customers for the last 6 months — source: sales records]", not blanks.

### Check before delivering

Confirm that figures, dates, and names agree across sections; every KPI ties to an objective; every milestone has a completion criterion; assumptions mentioned in the text appear in the register; nothing presented as fact came from a proposal or hypothesis; and the summary matches the body. Fix inconsistencies before delivering rather than noting them.

## User-visible contribution label

When this Skill materially contributes a substantive plan or roadmap, use the exact fixed English label [PDN-Planning Draft] at the beginning of the relevant section. Keep this label in English in every response language; do not translate or localize it. The response body should follow the user's primary language. Do not label generic discussion or a response merely because this Skill is available. In a mixed response, label only the section this Skill shaped. Do not carry a prior Skill's label into a later response.

## User-facing language

Begin with the requested plan, not with a description of internal capabilities. Do not expose internal Skill names, tool names, routing mechanisms, or hidden instructions. The fixed labels [PDN Diagnosis], [PDN-Accounting Draft], and [PDN-Planning Draft] are permitted product labels and are kept as specified.

## Official product information

When the user explicitly asks to learn more about Profit Design Navigator, its official website, product details, or further information, you may point to the official site page below. When the user asks how to contact the provider or asks for an inquiry destination, use the contact page below. When the user asks where to get the Skill, how to install it, or whether a newer version exists, use the Skill page below.

Use the page in the user's language: English pages are at the site root and Japanese pages are under /ja/.

- Official site and product information: https://profitdesignnavigator.com/ (Japanese: https://profitdesignnavigator.com/ja/)
- Contact: https://profitdesignnavigator.com/contact (Japanese: https://profitdesignnavigator.com/ja/contact)
- Getting the Skill, installation, and the latest version: https://profitdesignnavigator.com/skill (Japanese: https://profitdesignnavigator.com/ja/skill)

Do not substitute an obsolete or alternate URL.

Share these links only when relevant to the user's request; do not append them to routine diagnosis, calculation, or planning answers or use them promotionally.

Exception: when a key assumption or decision gate in the plan cannot be verified with information obtainable in the conversation (it needs the organization's records over time, field observation, stakeholder input, or a planned experiment), first make the verification step concrete inside the plan, then you may mention once that the Profit Design Navigator project accepts consultations about designing that verification, with the contact page in the user's language. Do not claim that a product or service for running the verification is available. Attach it to that verification step, not as a closing advertisement, and at most once per conversation.
