# Willyu1007 Mytrader Plan Maker

> Plan Maker

- Skill: `tomevault-io/willyu1007-mytrader-plan-maker` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/willyu1007-mytrader-plan-maker`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/willyu1007-mytrader-plan-maker/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/willyu1007-mytrader-plan-maker

---


# Plan Maker

## Purpose
Produce a single, goal-aligned macro-level roadmap as a Markdown document that can guide execution without modifying the codebase.

## When to use
Use the plan-maker skill when:
- **Strong trigger**: The user mentions "roadmap" (路线图) — MUST use the `plan-maker` skill
- The user asks for a plan/milestones/implementation plan (规划/方案/里程碑/实施计划) before coding
- The user asks to "align thinking first" (先对齐思路) before planning
- The task is large/ambiguous and benefits from staged execution and verification
- You need a roadmap artifact saved under `dev-docs/active/` for collaboration and handoff

Avoid the skill when:
- The change is trivial (<30 min) and does not benefit from staged execution/verification
- A roadmap already exists and only minor edits are needed (update the existing roadmap instead)

## Inputs
- Task goal (required)
  - If the goal is ambiguous or missing critical constraints, you MUST ask clarifying questions before drafting the roadmap.
- Requirements source (optional):
  - **Existing document**: User provides a path to an existing requirements document; plan-maker reads and extracts key points
  - **Interactive collection**: Collect requirements through Q&A dialogue with the user
  - **Both**: Read existing document AND supplement with interactive Q&A
- Requirements alignment mode (optional):
  - If user requests "align thinking first" (先对齐思路), generate requirements document to `dev-docs/active/<task>/requirement.md` before creating roadmap
  - See `./templates/requirement.md` for the requirements document template

## Outputs
- `dev-docs/active/<task>/roadmap.md` (always)
  - `<task>` is a short filesystem-safe slug derived from the goal and confirmed with the user.
- `dev-docs/active/<task>/requirement.md` (optional, when requirements alignment mode is active)
  - Generated when user requests "align thinking first" or provides existing requirements document

## Steps

### Phase 0 — Requirements alignment (optional, triggered by user request)

0. **Check for requirements alignment request**:
   - If user asks to "align thinking first" (先对齐思路) or provides an existing requirements document:
     - Proceed to step 0a
   - Otherwise, skip to step 1

0a. **Requirements source handling**:
   - If user provides an existing document path:
     - Read the document and extract: goal, use cases, boundaries, constraints
     - Summarize key points and confirm understanding with user
   - If user requests interactive collection:
     - Ask structured questions to collect:
       - Core goal (1 sentence)
       - Main use cases (2-5)
       - Boundaries / non-goals
       - Key constraints
     - Summarize collected requirements and confirm with user

0b. **Generate requirements document** (if alignment mode is active):
   - Propose `<task>` slug (if not yet confirmed)
   - Save aligned requirements to `dev-docs/active/<task>/requirement.md`
   - Confirm with user: "Requirements documented. Proceed to roadmap creation?"
   - If user confirms, continue to step 1
   - If user wants to refine, iterate on requirements document

### Phase 1 — Roadmap creation (core workflow)

1. Restate the goal in one sentence and confirm direction.
2. Identify what is unclear and ask clarifying questions.
   - Ask only what is necessary to align the roadmap to the goal (scope, non-goals, target environment, success criteria, constraints).
   - If the user cannot answer now, record assumptions explicitly and surface the risk.
   - If a requirements document exists at `dev-docs/active/<task>/requirement.md`, use `dev-docs/active/<task>/requirement.md` as input.
3. Propose a `<task>` slug and confirm the `<task>` slug with the user.
   - Use kebab-case; avoid dates unless requested.
   - If already confirmed in Phase 0, skip step 3.
4. Draft the roadmap using `./templates/roadmap.md`.
   - Keep the roadmap macro-level: phases, milestones, deliverables, verification, risks, rollback.
   - Only include specific file paths/APIs when you have evidence; otherwise add a discovery step.
   - Include an "Optional detailed documentation layout (convention)" section that declares the expected file layout under `dev-docs/active/<task>/` without creating those files.
5. Save the roadmap to `dev-docs/active/<task>/roadmap.md`.
6. Return a short handoff message to the user:
   - confirmed goal
   - where the roadmap was saved
   - the next 3 actions to start execution (without executing them)

### Phase 2 — dev-docs linkage (conditional)

7. **Evaluate dev-docs Decision Gate**:
   - Check if task meets any of these criteria:
     - Expected duration > 2 hours, or likely to span multiple sessions
     - Scope touches >= 2 modules/directories, or requires >= 3 sequential steps with verification
     - User explicitly needs handoff/context recovery artifacts
   - If criteria are met:
     - Inform user: "This task qualifies for a full dev-docs bundle for context preservation."
     - Ask: "Would you like to create the complete documentation bundle now?"
     - If user confirms, **trigger `create-dev-docs-plan` skill** with the roadmap as input
   - If criteria not met:
     - Note in the handoff message that roadmap is sufficient for the current task

## Verification
- [ ] Goal is restated and (where needed) confirmed with the user
- [ ] Ambiguities are resolved or recorded as explicit open questions/assumptions
- [ ] (If alignment mode) Requirements document saved to `dev-docs/active/<task>/requirement.md`
- [ ] (If alignment mode) User confirmed requirements understanding before roadmap creation
- [ ] Roadmap includes milestones/phases and per-step deliverables
- [ ] Roadmap defines verification/acceptance criteria and a rollback strategy
- [ ] Roadmap is saved to `dev-docs/active/<task>/roadmap.md`
- [ ] dev-docs Decision Gate evaluated; user prompted for full bundle if criteria met
- [ ] No application/source/config files were modified

## Boundaries
- MUST NOT modify application/source code, project configuration, or database state
- MUST ask clarifying questions when the goal or constraints are ambiguous
- MUST NOT invent project-specific facts (APIs, file paths, schemas) without evidence
- **MUST use the `plan-maker` skill when user mentions "roadmap"** (强触发关键词)
- If the user asks to implement immediately but the task is non-trivial, produce the roadmap first, then ask for confirmation to proceed with execution in a follow-up turn.
- If the task meets the dev-docs Decision Gate, **MUST prompt user** whether to continue with `create-dev-docs-plan`
- If user confirms dev-docs bundle creation, **MUST trigger `create-dev-docs-plan` skill**
- SHOULD keep the roadmap macro-level; deep design details belong in separate documentation artifacts
- SHOULD NOT include secrets (credentials, tokens, private keys) in the roadmap
- PRODUCES macro-level roadmaps: milestones, phases, scope, impact, risks, rollback strategy
- PRODUCES requirements documents (when alignment mode is active)
- DOES NOT produce implementation-level documentation (architecture diagrams, step-by-step code guides, pitfalls logs)
- The roadmap is a planning artifact; detailed implementation docs belong to a separate documentation bundle

## Included assets
- Templates:
  - `./templates/roadmap.md` (roadmap document)
  - `./templates/requirement.md` (requirements alignment document)
- Reference: `./reference/detailed-docs-convention.md` (optional file layout convention)
- Example: `./examples/sample-roadmap.md`

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/willyu1007) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-15 -->