bmad-method 6.10.1-next.2 → 6.10.1-next.21
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude-plugin/marketplace.json +52 -27
- package/package.json +4 -3
- package/removals.txt +5 -0
- package/src/bmm-skills/1-analysis/bmad-agent-analyst/customize.toml +19 -4
- package/src/bmm-skills/1-analysis/bmad-product-brief/SKILL.md +1 -1
- package/src/bmm-skills/1-analysis/bmad-product-brief/customize.toml +5 -3
- package/src/bmm-skills/2-plan-workflows/bmad-prd/SKILL.md +2 -0
- package/src/bmm-skills/2-plan-workflows/bmad-prd/customize.toml +5 -3
- package/src/{core-skills → bmm-skills/2-plan-workflows}/bmad-spec/SKILL.md +18 -3
- package/src/{core-skills → bmm-skills/2-plan-workflows}/bmad-spec/assets/spec-template.md +1 -1
- package/src/bmm-skills/2-plan-workflows/bmad-spec/assets/stories-schema.md +44 -0
- package/src/{core-skills → bmm-skills/2-plan-workflows}/bmad-spec/customize.toml +3 -4
- package/src/bmm-skills/2-plan-workflows/bmad-ux/customize.toml +4 -2
- package/src/bmm-skills/3-solutioning/bmad-architecture/SKILL.md +2 -2
- package/src/bmm-skills/3-solutioning/bmad-architecture/customize.toml +4 -2
- package/src/bmm-skills/4-implementation/bmad-agent-dev/customize.toml +3 -0
- package/src/bmm-skills/4-implementation/bmad-code-review/SKILL.md +2 -4
- package/src/bmm-skills/4-implementation/bmad-code-review/customize.toml +52 -0
- package/src/bmm-skills/4-implementation/bmad-code-review/steps/step-01-gather-context.md +0 -1
- package/src/bmm-skills/4-implementation/bmad-code-review/steps/step-02-review.md +10 -24
- package/src/bmm-skills/4-implementation/bmad-code-review/steps/step-03-triage.md +3 -4
- package/src/bmm-skills/4-implementation/bmad-dev-auto/SKILL.md +33 -12
- package/src/bmm-skills/4-implementation/bmad-dev-auto/customize.toml +75 -0
- package/src/bmm-skills/4-implementation/bmad-dev-auto/spec-template.md +4 -4
- package/src/bmm-skills/4-implementation/bmad-dev-auto/step-01-clarify-and-route.md +22 -4
- package/src/bmm-skills/4-implementation/bmad-dev-auto/step-02-plan.md +5 -6
- package/src/bmm-skills/4-implementation/bmad-dev-auto/step-03-implement.md +8 -4
- package/src/bmm-skills/4-implementation/bmad-dev-auto/step-04-review.md +13 -19
- package/src/bmm-skills/4-implementation/bmad-dev-story/customize.toml +3 -0
- package/src/bmm-skills/4-implementation/bmad-quick-dev/SKILL.md +6 -108
- package/src/bmm-skills/4-implementation/bmad-quick-dev/customize.toml +73 -0
- package/src/bmm-skills/4-implementation/bmad-quick-dev/render.py +381 -0
- package/src/bmm-skills/4-implementation/bmad-quick-dev/spec-template.md +2 -2
- package/src/bmm-skills/4-implementation/bmad-quick-dev/step-01-clarify-and-route.md +11 -13
- package/src/bmm-skills/4-implementation/bmad-quick-dev/step-02-plan.md +4 -9
- package/src/bmm-skills/4-implementation/bmad-quick-dev/step-03-implement.md +12 -4
- package/src/bmm-skills/4-implementation/bmad-quick-dev/step-04-review.md +8 -20
- package/src/bmm-skills/4-implementation/bmad-quick-dev/step-05-present.md +4 -4
- package/src/bmm-skills/4-implementation/bmad-quick-dev/step-oneshot.md +12 -13
- package/src/bmm-skills/4-implementation/bmad-quick-dev/sync-sprint-status.md +6 -6
- package/src/bmm-skills/4-implementation/bmad-quick-dev/workflow.md +85 -0
- package/src/bmm-skills/module-help.csv +2 -4
- package/src/bmm-skills/module.yaml +2 -5
- package/src/bmm-skills/v6-shims/README.md +24 -0
- package/src/bmm-skills/{3-solutioning → v6-shims}/bmad-create-architecture/SKILL.md +1 -1
- package/src/bmm-skills/{2-plan-workflows → v6-shims}/bmad-create-prd/SKILL.md +3 -3
- package/src/bmm-skills/v6-shims/bmad-domain-research/SKILL.md +14 -0
- package/src/bmm-skills/{2-plan-workflows → v6-shims}/bmad-edit-prd/SKILL.md +3 -3
- package/src/bmm-skills/v6-shims/bmad-market-research/SKILL.md +14 -0
- package/src/bmm-skills/v6-shims/bmad-technical-research/SKILL.md +14 -0
- package/src/bmm-skills/{2-plan-workflows → v6-shims}/bmad-validate-prd/SKILL.md +3 -3
- package/src/core-skills/bmad-advanced-elicitation/SKILL.md +26 -103
- package/src/core-skills/bmad-advanced-elicitation/customize.toml +54 -0
- package/src/core-skills/bmad-advanced-elicitation/scripts/pick_methods.py +233 -0
- package/src/core-skills/bmad-advanced-elicitation/scripts/tests/test_pick_methods.py +228 -0
- package/src/core-skills/bmad-brainstorming/SKILL.md +3 -3
- package/src/core-skills/bmad-brainstorming/assets/brain-selector.html +2 -0
- package/src/core-skills/bmad-brainstorming/references/mode-autonomous.md +1 -1
- package/src/core-skills/bmad-brainstorming/scripts/brain.py +36 -6
- package/src/core-skills/bmad-brainstorming/scripts/tests/test_brain.py +22 -0
- package/src/core-skills/bmad-customize/SKILL.md +2 -2
- package/src/core-skills/bmad-deep-recon/SKILL.md +82 -0
- package/src/core-skills/bmad-deep-recon/assets/research.template.md +18 -0
- package/src/core-skills/bmad-deep-recon/customize.toml +212 -0
- package/src/core-skills/bmad-deep-recon/references/draft.md +8 -0
- package/src/core-skills/bmad-deep-recon/references/finalize.md +11 -0
- package/src/core-skills/bmad-deep-recon/references/html-briefing.md +16 -0
- package/src/core-skills/bmad-deep-recon/references/lifecycle.md +11 -0
- package/src/core-skills/bmad-deep-recon/references/process.md +10 -0
- package/src/core-skills/bmad-deep-recon/references/run.md +73 -0
- package/src/core-skills/bmad-deep-recon/references/selection.md +13 -0
- package/src/core-skills/bmad-deep-recon/references/synthesis.md +16 -0
- package/src/core-skills/bmad-deep-recon/references/verification.md +29 -0
- package/src/core-skills/bmad-deep-recon/scripts/recon_kit.py +322 -0
- package/src/core-skills/bmad-deep-recon/scripts/tests/test_recon_kit.py +144 -0
- package/src/core-skills/bmad-deep-recon/types/academic-lit.md +19 -0
- package/src/core-skills/bmad-deep-recon/types/competitive.md +19 -0
- package/src/core-skills/bmad-deep-recon/types/domain.md +19 -0
- package/src/core-skills/bmad-deep-recon/types/market.md +19 -0
- package/src/core-skills/bmad-deep-recon/types/technical.md +19 -0
- package/src/core-skills/bmad-deep-recon/types/user-voice.md +19 -0
- package/src/core-skills/bmad-forge-idea/SKILL.md +2 -2
- package/src/core-skills/bmad-forge-idea/scripts/resolve_personas.py +4 -1
- package/src/core-skills/bmad-help/SKILL.md +1 -1
- package/src/core-skills/bmad-party-mode/SKILL.md +2 -2
- package/src/core-skills/bmad-party-mode/scripts/resolve_party.py +11 -3
- package/src/core-skills/bmad-review/SKILL.md +49 -0
- package/src/core-skills/bmad-review/customize.toml +141 -0
- package/src/core-skills/bmad-review/references/editorial-common.md +56 -0
- package/src/core-skills/bmad-review/references/lens-adversarial.md +18 -0
- package/src/core-skills/bmad-review/references/lens-edge-case-hunter.md +54 -0
- package/src/core-skills/bmad-review/references/lens-prose.md +7 -0
- package/src/core-skills/bmad-review/references/lens-structure.md +9 -0
- package/src/core-skills/{bmad-review-verification-gap/SKILL.md → bmad-review/references/lens-verification-gap.md} +15 -39
- package/src/core-skills/bmad-review/references/structure-models.md +44 -0
- package/src/core-skills/bmad-review/scripts/tests/test_word_metrics.py +62 -0
- package/src/core-skills/bmad-review/scripts/word_metrics.py +102 -0
- package/src/core-skills/module-help.csv +3 -7
- package/src/core-skills/module.yaml +5 -0
- package/src/core-skills/v6-shims/README.md +25 -0
- package/src/core-skills/v6-shims/bmad-editorial-review/SKILL.md +6 -0
- package/src/core-skills/v6-shims/bmad-editorial-review/customize.toml +31 -0
- package/src/core-skills/v6-shims/bmad-editorial-review-prose/SKILL.md +6 -0
- package/src/core-skills/v6-shims/bmad-editorial-review-structure/SKILL.md +6 -0
- package/src/core-skills/v6-shims/bmad-review-adversarial-general/SKILL.md +6 -0
- package/src/core-skills/v6-shims/bmad-review-edge-case-hunter/SKILL.md +6 -0
- package/src/core-skills/v6-shims/bmad-review-verification-gap/SKILL.md +6 -0
- package/tools/installer/ide/platform-codes.yaml +7 -0
- package/tools/installer/modules/custom-module-manager.js +12 -6
- package/tools/installer/modules/external-manager.js +12 -8
- package/tools/installer/modules/git-env.js +47 -0
- package/tools/skill-validator.md +11 -1
- package/tools/validate-skills.js +33 -0
- package/src/bmm-skills/1-analysis/research/bmad-domain-research/SKILL.md +0 -96
- package/src/bmm-skills/1-analysis/research/bmad-domain-research/customize.toml +0 -41
- package/src/bmm-skills/1-analysis/research/bmad-domain-research/domain-steps/step-01-init.md +0 -137
- package/src/bmm-skills/1-analysis/research/bmad-domain-research/domain-steps/step-02-domain-analysis.md +0 -229
- package/src/bmm-skills/1-analysis/research/bmad-domain-research/domain-steps/step-03-competitive-landscape.md +0 -238
- package/src/bmm-skills/1-analysis/research/bmad-domain-research/domain-steps/step-04-regulatory-focus.md +0 -206
- package/src/bmm-skills/1-analysis/research/bmad-domain-research/domain-steps/step-05-technical-trends.md +0 -234
- package/src/bmm-skills/1-analysis/research/bmad-domain-research/domain-steps/step-06-research-synthesis.md +0 -450
- package/src/bmm-skills/1-analysis/research/bmad-domain-research/research.template.md +0 -29
- package/src/bmm-skills/1-analysis/research/bmad-market-research/SKILL.md +0 -96
- package/src/bmm-skills/1-analysis/research/bmad-market-research/customize.toml +0 -41
- package/src/bmm-skills/1-analysis/research/bmad-market-research/research.template.md +0 -29
- package/src/bmm-skills/1-analysis/research/bmad-market-research/steps/step-01-init.md +0 -184
- package/src/bmm-skills/1-analysis/research/bmad-market-research/steps/step-02-customer-behavior.md +0 -239
- package/src/bmm-skills/1-analysis/research/bmad-market-research/steps/step-03-customer-pain-points.md +0 -251
- package/src/bmm-skills/1-analysis/research/bmad-market-research/steps/step-04-customer-decisions.md +0 -261
- package/src/bmm-skills/1-analysis/research/bmad-market-research/steps/step-05-competitive-analysis.md +0 -173
- package/src/bmm-skills/1-analysis/research/bmad-market-research/steps/step-06-research-completion.md +0 -484
- package/src/bmm-skills/1-analysis/research/bmad-technical-research/SKILL.md +0 -96
- package/src/bmm-skills/1-analysis/research/bmad-technical-research/customize.toml +0 -41
- package/src/bmm-skills/1-analysis/research/bmad-technical-research/research.template.md +0 -29
- package/src/bmm-skills/1-analysis/research/bmad-technical-research/technical-steps/step-01-init.md +0 -137
- package/src/bmm-skills/1-analysis/research/bmad-technical-research/technical-steps/step-02-technical-overview.md +0 -239
- package/src/bmm-skills/1-analysis/research/bmad-technical-research/technical-steps/step-03-integration-patterns.md +0 -248
- package/src/bmm-skills/1-analysis/research/bmad-technical-research/technical-steps/step-04-architectural-patterns.md +0 -202
- package/src/bmm-skills/1-analysis/research/bmad-technical-research/technical-steps/step-05-implementation-research.md +0 -233
- package/src/bmm-skills/1-analysis/research/bmad-technical-research/technical-steps/step-06-research-synthesis.md +0 -493
- package/src/core-skills/bmad-brainstorming/analysis/catalog-analysis.md +0 -239
- package/src/core-skills/bmad-brainstorming/analysis/method-matrix.csv +0 -109
- package/src/core-skills/bmad-editorial-review-prose/SKILL.md +0 -86
- package/src/core-skills/bmad-editorial-review-structure/SKILL.md +0 -179
- package/src/core-skills/bmad-index-docs/SKILL.md +0 -66
- package/src/core-skills/bmad-review-adversarial-general/SKILL.md +0 -37
- package/src/core-skills/bmad-review-edge-case-hunter/SKILL.md +0 -73
- package/src/core-skills/bmad-review-edge-case-hunter/references/deletion-check.md +0 -14
- package/src/core-skills/bmad-shard-doc/SKILL.md +0 -105
- /package/src/{core-skills → bmm-skills/2-plan-workflows}/bmad-spec/assets/headless-schemas.md +0 -0
- /package/src/bmm-skills/{3-solutioning → v6-shims}/bmad-create-architecture/customize.toml +0 -0
- /package/src/bmm-skills/{2-plan-workflows → v6-shims}/bmad-create-prd/customize.toml +0 -0
- /package/src/bmm-skills/{2-plan-workflows → v6-shims}/bmad-edit-prd/customize.toml +0 -0
- /package/src/bmm-skills/{2-plan-workflows → v6-shims}/bmad-validate-prd/customize.toml +0 -0
- /package/src/core-skills/bmad-advanced-elicitation/{methods.csv → assets/methods.csv} +0 -0
- /package/src/core-skills/bmad-party-mode/scripts/tests/{test-resolve_party.py → test_resolve_party.py} +0 -0
|
@@ -1,96 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: bmad-domain-research
|
|
3
|
-
description: 'Conduct domain and industry research. Use when the user says wants to do domain research for a topic or industry'
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
# Domain Research Workflow
|
|
7
|
-
|
|
8
|
-
**Goal:** Conduct comprehensive domain/industry research using current web data and verified sources to produce complete research documents with compelling narratives and proper citations.
|
|
9
|
-
|
|
10
|
-
**Your Role:** You are a domain research facilitator working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings domain knowledge and research direction.
|
|
11
|
-
|
|
12
|
-
## Conventions
|
|
13
|
-
|
|
14
|
-
- Bare paths (e.g. `domain-steps/step-01-init.md`) resolve from the skill root.
|
|
15
|
-
- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
|
|
16
|
-
- `{project-root}`-prefixed paths resolve from the project working directory.
|
|
17
|
-
- `{skill-name}` resolves to the skill directory's basename.
|
|
18
|
-
|
|
19
|
-
## PREREQUISITE
|
|
20
|
-
|
|
21
|
-
**⛔ Web search required.** If unavailable, abort and tell the user.
|
|
22
|
-
|
|
23
|
-
## On Activation
|
|
24
|
-
|
|
25
|
-
### Step 1: Resolve the Workflow Block
|
|
26
|
-
|
|
27
|
-
Run: `python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow`
|
|
28
|
-
|
|
29
|
-
**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
|
|
30
|
-
|
|
31
|
-
1. `{skill-root}/customize.toml` — defaults
|
|
32
|
-
2. `{project-root}/_bmad/custom/{skill-name}.toml` — team overrides
|
|
33
|
-
3. `{project-root}/_bmad/custom/{skill-name}.user.toml` — personal overrides
|
|
34
|
-
|
|
35
|
-
Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.
|
|
36
|
-
|
|
37
|
-
### Step 2: Execute Prepend Steps
|
|
38
|
-
|
|
39
|
-
Execute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.
|
|
40
|
-
|
|
41
|
-
### Step 3: Load Persistent Facts
|
|
42
|
-
|
|
43
|
-
Treat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.
|
|
44
|
-
|
|
45
|
-
### Step 4: Load Config
|
|
46
|
-
|
|
47
|
-
Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
|
|
48
|
-
- Use `{user_name}` for greeting
|
|
49
|
-
- Use `{communication_language}` for all communications
|
|
50
|
-
- Use `{document_output_language}` for output documents
|
|
51
|
-
- Use `{planning_artifacts}` for output location and artifact scanning
|
|
52
|
-
- Use `{project_knowledge}` for additional context scanning
|
|
53
|
-
|
|
54
|
-
### Step 5: Greet the User
|
|
55
|
-
|
|
56
|
-
Greet `{user_name}`, speaking in `{communication_language}`.
|
|
57
|
-
|
|
58
|
-
### Step 6: Execute Append Steps
|
|
59
|
-
|
|
60
|
-
Execute each entry in `{workflow.activation_steps_append}` in order.
|
|
61
|
-
|
|
62
|
-
Activation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding. Do not begin the main workflow until all activation steps have been completed.
|
|
63
|
-
|
|
64
|
-
## QUICK TOPIC DISCOVERY
|
|
65
|
-
|
|
66
|
-
"Welcome {{user_name}}! Let's get started with your **domain/industry research**.
|
|
67
|
-
|
|
68
|
-
**What domain, industry, or sector do you want to research?**
|
|
69
|
-
|
|
70
|
-
For example:
|
|
71
|
-
- 'The healthcare technology industry'
|
|
72
|
-
- 'Sustainable packaging regulations in Europe'
|
|
73
|
-
- 'Construction and building materials sector'
|
|
74
|
-
- 'Or any other domain you have in mind...'"
|
|
75
|
-
|
|
76
|
-
### Topic Clarification
|
|
77
|
-
|
|
78
|
-
Based on the user's topic, briefly clarify:
|
|
79
|
-
1. **Core Domain**: "What specific aspect of [domain] are you most interested in?"
|
|
80
|
-
2. **Research Goals**: "What do you hope to achieve with this research?"
|
|
81
|
-
3. **Scope**: "Should we focus broadly or dive deep into specific aspects?"
|
|
82
|
-
|
|
83
|
-
## ROUTE TO DOMAIN RESEARCH STEPS
|
|
84
|
-
|
|
85
|
-
After gathering the topic and goals:
|
|
86
|
-
|
|
87
|
-
1. Set `research_type = "domain"`
|
|
88
|
-
2. Set `research_topic = [discovered topic from discussion]`
|
|
89
|
-
3. Set `research_goals = [discovered goals from discussion]`
|
|
90
|
-
4. Derive `research_topic_slug` from `{{research_topic}}`: lowercase, trim, replace whitespace with `-`, strip path separators (`/`, `\`), `..`, and any character that is not alphanumeric, `-`, or `_`. Collapse repeated `-` and strip leading/trailing `-`. If the result is empty, use `untitled`.
|
|
91
|
-
5. Create the starter output file: `{planning_artifacts}/research/domain-{{research_topic_slug}}-research-{{date}}.md` with exact copy of the `./research.template.md` contents
|
|
92
|
-
6. Load: `./domain-steps/step-01-init.md` with topic context
|
|
93
|
-
|
|
94
|
-
**Note:** The discovered topic from the discussion should be passed to the initialization step, so it doesn't need to ask "What do you want to research?" again - it can focus on refining the scope for domain research.
|
|
95
|
-
|
|
96
|
-
**✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`**
|
|
@@ -1,41 +0,0 @@
|
|
|
1
|
-
# DO NOT EDIT -- overwritten on every update.
|
|
2
|
-
#
|
|
3
|
-
# Workflow customization surface for bmad-domain-research. Mirrors the
|
|
4
|
-
# agent customization shape under the [workflow] namespace.
|
|
5
|
-
|
|
6
|
-
[workflow]
|
|
7
|
-
|
|
8
|
-
# --- Configurable below. Overrides merge per BMad structural rules: ---
|
|
9
|
-
# scalars: override wins • arrays (persistent_facts, activation_steps_*): append
|
|
10
|
-
# arrays-of-tables with `code`/`id`: replace matching items, append new ones.
|
|
11
|
-
|
|
12
|
-
# Steps to run before the standard activation (config load, greet).
|
|
13
|
-
# Overrides append. Use for pre-flight loads, compliance checks, etc.
|
|
14
|
-
|
|
15
|
-
activation_steps_prepend = []
|
|
16
|
-
|
|
17
|
-
# Steps to run after greet but before the workflow begins.
|
|
18
|
-
# Overrides append. Use for context-heavy setup that should happen
|
|
19
|
-
# once the user has been acknowledged.
|
|
20
|
-
|
|
21
|
-
activation_steps_append = []
|
|
22
|
-
|
|
23
|
-
# Persistent facts the workflow keeps in mind for the whole run
|
|
24
|
-
# (standards, compliance constraints, stylistic guardrails).
|
|
25
|
-
# Distinct from the runtime memory sidecar — these are static context
|
|
26
|
-
# loaded on activation. Overrides append.
|
|
27
|
-
#
|
|
28
|
-
# Each entry is either:
|
|
29
|
-
# - a literal sentence, e.g. "All briefs must include a regulatory-risk section."
|
|
30
|
-
# - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
|
|
31
|
-
# (glob patterns are supported; the file's contents are loaded and treated as facts).
|
|
32
|
-
|
|
33
|
-
persistent_facts = [
|
|
34
|
-
"file:{project-root}/**/project-context.md",
|
|
35
|
-
]
|
|
36
|
-
|
|
37
|
-
# Scalar: executed when the workflow reaches its terminal stage (Step 6: Research Synthesis),
|
|
38
|
-
# after the domain research document has been saved and the user selects [C] Complete.
|
|
39
|
-
# Override wins. Leave empty for no custom post-completion behavior.
|
|
40
|
-
|
|
41
|
-
on_complete = ""
|
package/src/bmm-skills/1-analysis/research/bmad-domain-research/domain-steps/step-01-init.md
DELETED
|
@@ -1,137 +0,0 @@
|
|
|
1
|
-
# Domain Research Step 1: Domain Research Scope Confirmation
|
|
2
|
-
|
|
3
|
-
## MANDATORY EXECUTION RULES (READ FIRST):
|
|
4
|
-
|
|
5
|
-
- 🛑 NEVER generate content without user confirmation
|
|
6
|
-
|
|
7
|
-
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
|
8
|
-
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
|
9
|
-
- ✅ FOCUS EXCLUSIVELY on confirming domain research scope and approach
|
|
10
|
-
- 📋 YOU ARE A DOMAIN RESEARCH PLANNER, not content generator
|
|
11
|
-
- 💬 ACKNOWLEDGE and CONFIRM understanding of domain research goals
|
|
12
|
-
- 🔍 This is SCOPE CONFIRMATION ONLY - no web research yet
|
|
13
|
-
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
|
14
|
-
|
|
15
|
-
## EXECUTION PROTOCOLS:
|
|
16
|
-
|
|
17
|
-
- 🎯 Show your analysis before taking any action
|
|
18
|
-
- ⚠️ Present [C] continue option after scope confirmation
|
|
19
|
-
- 💾 ONLY proceed when user chooses C (Continue)
|
|
20
|
-
- 📖 Update frontmatter `stepsCompleted: [1]` before loading next step
|
|
21
|
-
- 🚫 FORBIDDEN to load next step until C is selected
|
|
22
|
-
|
|
23
|
-
## CONTEXT BOUNDARIES:
|
|
24
|
-
|
|
25
|
-
- Research type = "domain" is already set
|
|
26
|
-
- **Research topic = "{{research_topic}}"** - discovered from initial discussion
|
|
27
|
-
- **Research goals = "{{research_goals}}"** - captured from initial discussion
|
|
28
|
-
- Focus on industry/domain analysis with web research
|
|
29
|
-
- Web search is required to verify and supplement your knowledge with current facts
|
|
30
|
-
|
|
31
|
-
## YOUR TASK:
|
|
32
|
-
|
|
33
|
-
Confirm domain research scope and approach for **{{research_topic}}** with the user's goals in mind.
|
|
34
|
-
|
|
35
|
-
## DOMAIN SCOPE CONFIRMATION:
|
|
36
|
-
|
|
37
|
-
### 1. Begin Scope Confirmation
|
|
38
|
-
|
|
39
|
-
Start with domain scope understanding:
|
|
40
|
-
"I understand you want to conduct **domain research** for **{{research_topic}}** with these goals: {{research_goals}}
|
|
41
|
-
|
|
42
|
-
**Domain Research Scope:**
|
|
43
|
-
|
|
44
|
-
- **Industry Analysis**: Industry structure, market dynamics, and competitive landscape
|
|
45
|
-
- **Regulatory Environment**: Compliance requirements, regulations, and standards
|
|
46
|
-
- **Technology Patterns**: Innovation trends, technology adoption, and digital transformation
|
|
47
|
-
- **Economic Factors**: Market size, growth trends, and economic impact
|
|
48
|
-
- **Supply Chain**: Value chain analysis and ecosystem relationships
|
|
49
|
-
|
|
50
|
-
**Research Approach:**
|
|
51
|
-
|
|
52
|
-
- All claims verified against current public sources
|
|
53
|
-
- Multi-source validation for critical domain claims
|
|
54
|
-
- Confidence levels for uncertain domain information
|
|
55
|
-
- Comprehensive domain coverage with industry-specific insights
|
|
56
|
-
|
|
57
|
-
### 2. Scope Confirmation
|
|
58
|
-
|
|
59
|
-
Present clear scope confirmation:
|
|
60
|
-
"**Domain Research Scope Confirmation:**
|
|
61
|
-
|
|
62
|
-
For **{{research_topic}}**, I will research:
|
|
63
|
-
|
|
64
|
-
✅ **Industry Analysis** - market structure, key players, competitive dynamics
|
|
65
|
-
✅ **Regulatory Requirements** - compliance standards, legal frameworks
|
|
66
|
-
✅ **Technology Trends** - innovation patterns, digital transformation
|
|
67
|
-
✅ **Economic Factors** - market size, growth projections, economic impact
|
|
68
|
-
✅ **Supply Chain Analysis** - value chain, ecosystem, partnerships
|
|
69
|
-
|
|
70
|
-
**All claims verified against current public sources.**
|
|
71
|
-
|
|
72
|
-
**Does this domain research scope and approach align with your goals?**
|
|
73
|
-
[C] Continue - Begin domain research with this scope
|
|
74
|
-
|
|
75
|
-
### 3. Handle Continue Selection
|
|
76
|
-
|
|
77
|
-
#### If 'C' (Continue):
|
|
78
|
-
|
|
79
|
-
- Document scope confirmation in research file
|
|
80
|
-
- Update frontmatter: `stepsCompleted: [1]`
|
|
81
|
-
- Load: `./step-02-domain-analysis.md`
|
|
82
|
-
|
|
83
|
-
## APPEND TO DOCUMENT:
|
|
84
|
-
|
|
85
|
-
When user selects 'C', append scope confirmation:
|
|
86
|
-
|
|
87
|
-
```markdown
|
|
88
|
-
## Domain Research Scope Confirmation
|
|
89
|
-
|
|
90
|
-
**Research Topic:** {{research_topic}}
|
|
91
|
-
**Research Goals:** {{research_goals}}
|
|
92
|
-
|
|
93
|
-
**Domain Research Scope:**
|
|
94
|
-
|
|
95
|
-
- Industry Analysis - market structure, competitive landscape
|
|
96
|
-
- Regulatory Environment - compliance requirements, legal frameworks
|
|
97
|
-
- Technology Trends - innovation patterns, digital transformation
|
|
98
|
-
- Economic Factors - market size, growth projections
|
|
99
|
-
- Supply Chain Analysis - value chain, ecosystem relationships
|
|
100
|
-
|
|
101
|
-
**Research Methodology:**
|
|
102
|
-
|
|
103
|
-
- All claims verified against current public sources
|
|
104
|
-
- Multi-source validation for critical domain claims
|
|
105
|
-
- Confidence level framework for uncertain information
|
|
106
|
-
- Comprehensive domain coverage with industry-specific insights
|
|
107
|
-
|
|
108
|
-
**Scope Confirmed:** {{date}}
|
|
109
|
-
```
|
|
110
|
-
|
|
111
|
-
## SUCCESS METRICS:
|
|
112
|
-
|
|
113
|
-
✅ Domain research scope clearly confirmed with user
|
|
114
|
-
✅ All domain analysis areas identified and explained
|
|
115
|
-
✅ Research methodology emphasized
|
|
116
|
-
✅ [C] continue option presented and handled correctly
|
|
117
|
-
✅ Scope confirmation documented when user proceeds
|
|
118
|
-
✅ Proper routing to next domain research step
|
|
119
|
-
|
|
120
|
-
## FAILURE MODES:
|
|
121
|
-
|
|
122
|
-
❌ Not clearly confirming domain research scope with user
|
|
123
|
-
❌ Missing critical domain analysis areas
|
|
124
|
-
❌ Not explaining that web search is required for current facts
|
|
125
|
-
❌ Not presenting [C] continue option
|
|
126
|
-
❌ Proceeding without user scope confirmation
|
|
127
|
-
❌ Not routing to next domain research step
|
|
128
|
-
|
|
129
|
-
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
|
|
130
|
-
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
|
131
|
-
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
|
132
|
-
|
|
133
|
-
## NEXT STEP:
|
|
134
|
-
|
|
135
|
-
After user selects 'C', load `./step-02-domain-analysis.md` to begin industry analysis.
|
|
136
|
-
|
|
137
|
-
Remember: This is SCOPE CONFIRMATION ONLY - no actual domain research yet, just confirming the research approach and scope!
|
|
@@ -1,229 +0,0 @@
|
|
|
1
|
-
# Domain Research Step 2: Industry Analysis
|
|
2
|
-
|
|
3
|
-
## MANDATORY EXECUTION RULES (READ FIRST):
|
|
4
|
-
|
|
5
|
-
- 🛑 NEVER generate content without web search verification
|
|
6
|
-
|
|
7
|
-
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
|
8
|
-
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
|
9
|
-
- ✅ Search the web to verify and supplement your knowledge with current facts
|
|
10
|
-
- 📋 YOU ARE AN INDUSTRY ANALYST, not content generator
|
|
11
|
-
- 💬 FOCUS on market size, growth, and industry dynamics
|
|
12
|
-
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
|
13
|
-
- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
|
|
14
|
-
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
|
15
|
-
|
|
16
|
-
## EXECUTION PROTOCOLS:
|
|
17
|
-
|
|
18
|
-
- 🎯 Show web search analysis before presenting findings
|
|
19
|
-
- ⚠️ Present [C] continue option after industry analysis content generation
|
|
20
|
-
- 📝 WRITE INDUSTRY ANALYSIS TO DOCUMENT IMMEDIATELY
|
|
21
|
-
- 💾 ONLY proceed when user chooses C (Continue)
|
|
22
|
-
- 📖 Update frontmatter `stepsCompleted: [1, 2]` before loading next step
|
|
23
|
-
- 🚫 FORBIDDEN to load next step until C is selected
|
|
24
|
-
|
|
25
|
-
## CONTEXT BOUNDARIES:
|
|
26
|
-
|
|
27
|
-
- Current document and frontmatter from step-01 are available
|
|
28
|
-
- **Research topic = "{{research_topic}}"** - established from initial discussion
|
|
29
|
-
- **Research goals = "{{research_goals}}"** - established from initial discussion
|
|
30
|
-
- Focus on market size, growth, and industry dynamics
|
|
31
|
-
- Web search capabilities with source verification are enabled
|
|
32
|
-
|
|
33
|
-
## YOUR TASK:
|
|
34
|
-
|
|
35
|
-
Conduct industry analysis focusing on market size, growth, and industry dynamics. Search the web to verify and supplement current facts.
|
|
36
|
-
|
|
37
|
-
## INDUSTRY ANALYSIS SEQUENCE:
|
|
38
|
-
|
|
39
|
-
### 1. Begin Industry Analysis
|
|
40
|
-
|
|
41
|
-
**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different industry areas simultaneously and thoroughly.
|
|
42
|
-
|
|
43
|
-
Start with industry research approach:
|
|
44
|
-
"Now I'll conduct **industry analysis** for **{{research_topic}}** to understand market dynamics.
|
|
45
|
-
|
|
46
|
-
**Industry Analysis Focus:**
|
|
47
|
-
|
|
48
|
-
- Market size and valuation metrics
|
|
49
|
-
- Growth rates and market dynamics
|
|
50
|
-
- Market segmentation and structure
|
|
51
|
-
- Industry trends and evolution patterns
|
|
52
|
-
- Economic impact and value creation
|
|
53
|
-
|
|
54
|
-
**Let me search for current industry insights.**"
|
|
55
|
-
|
|
56
|
-
### 2. Parallel Industry Research Execution
|
|
57
|
-
|
|
58
|
-
**Execute multiple web searches simultaneously:**
|
|
59
|
-
|
|
60
|
-
Search the web: "{{research_topic}} market size value"
|
|
61
|
-
Search the web: "{{research_topic}} market growth rate dynamics"
|
|
62
|
-
Search the web: "{{research_topic}} market segmentation structure"
|
|
63
|
-
Search the web: "{{research_topic}} industry trends evolution"
|
|
64
|
-
|
|
65
|
-
**Analysis approach:**
|
|
66
|
-
|
|
67
|
-
- Look for recent market research reports and industry analyses
|
|
68
|
-
- Search for authoritative sources (market research firms, industry associations)
|
|
69
|
-
- Identify market size, growth rates, and segmentation data
|
|
70
|
-
- Research industry trends and evolution patterns
|
|
71
|
-
- Analyze economic impact and value creation metrics
|
|
72
|
-
|
|
73
|
-
### 3. Analyze and Aggregate Results
|
|
74
|
-
|
|
75
|
-
**Collect and analyze findings from all parallel searches:**
|
|
76
|
-
|
|
77
|
-
"After executing comprehensive parallel web searches, let me analyze and aggregate industry findings:
|
|
78
|
-
|
|
79
|
-
**Research Coverage:**
|
|
80
|
-
|
|
81
|
-
- Market size and valuation analysis
|
|
82
|
-
- Growth rates and market dynamics
|
|
83
|
-
- Market segmentation and structure
|
|
84
|
-
- Industry trends and evolution patterns
|
|
85
|
-
|
|
86
|
-
**Cross-Industry Analysis:**
|
|
87
|
-
[Identify patterns connecting market dynamics, segmentation, and trends]
|
|
88
|
-
|
|
89
|
-
**Quality Assessment:**
|
|
90
|
-
[Overall confidence levels and research gaps identified]"
|
|
91
|
-
|
|
92
|
-
### 4. Generate Industry Analysis Content
|
|
93
|
-
|
|
94
|
-
**WRITE IMMEDIATELY TO DOCUMENT**
|
|
95
|
-
|
|
96
|
-
Prepare industry analysis with web search citations:
|
|
97
|
-
|
|
98
|
-
#### Content Structure:
|
|
99
|
-
|
|
100
|
-
When saving to document, append these Level 2 and Level 3 sections:
|
|
101
|
-
|
|
102
|
-
```markdown
|
|
103
|
-
## Industry Analysis
|
|
104
|
-
|
|
105
|
-
### Market Size and Valuation
|
|
106
|
-
|
|
107
|
-
[Market size analysis with source citations]
|
|
108
|
-
_Total Market Size: [Current market valuation]_
|
|
109
|
-
_Growth Rate: [CAGR and market growth projections]_
|
|
110
|
-
_Market Segments: [Size and value of key market segments]_
|
|
111
|
-
_Economic Impact: [Economic contribution and value creation]_
|
|
112
|
-
_Source: [URL]_
|
|
113
|
-
|
|
114
|
-
### Market Dynamics and Growth
|
|
115
|
-
|
|
116
|
-
[Market dynamics analysis with source citations]
|
|
117
|
-
_Growth Drivers: [Key factors driving market growth]_
|
|
118
|
-
_Growth Barriers: [Factors limiting market expansion]_
|
|
119
|
-
_Cyclical Patterns: [Industry seasonality and cycles]_
|
|
120
|
-
_Market Maturity: [Life cycle stage and development phase]_
|
|
121
|
-
_Source: [URL]_
|
|
122
|
-
|
|
123
|
-
### Market Structure and Segmentation
|
|
124
|
-
|
|
125
|
-
[Market structure analysis with source citations]
|
|
126
|
-
_Primary Segments: [Key market segments and their characteristics]_
|
|
127
|
-
_Sub-segment Analysis: [Detailed breakdown of market sub-segments]_
|
|
128
|
-
_Geographic Distribution: [Regional market variations and concentrations]_
|
|
129
|
-
_Vertical Integration: [Supply chain and value chain structure]_
|
|
130
|
-
_Source: [URL]_
|
|
131
|
-
|
|
132
|
-
### Industry Trends and Evolution
|
|
133
|
-
|
|
134
|
-
[Industry trends analysis with source citations]
|
|
135
|
-
_Emerging Trends: [Current industry developments and transformations]_
|
|
136
|
-
_Historical Evolution: [Industry development over recent years]_
|
|
137
|
-
_Technology Integration: [How technology is changing the industry]_
|
|
138
|
-
_Future Outlook: [Projected industry developments and changes]_
|
|
139
|
-
_Source: [URL]_
|
|
140
|
-
|
|
141
|
-
### Competitive Dynamics
|
|
142
|
-
|
|
143
|
-
[Competitive dynamics analysis with source citations]
|
|
144
|
-
_Market Concentration: [Level of market consolidation and competition]_
|
|
145
|
-
_Competitive Intensity: [Degree of competition and rivalry]_
|
|
146
|
-
_Barriers to Entry: [Obstacles for new market entrants]_
|
|
147
|
-
_Innovation Pressure: [Rate of innovation and change]_
|
|
148
|
-
_Source: [URL]_
|
|
149
|
-
```
|
|
150
|
-
|
|
151
|
-
### 5. Present Analysis and Continue Option
|
|
152
|
-
|
|
153
|
-
**Show analysis and present continue option:**
|
|
154
|
-
|
|
155
|
-
"I've completed **industry analysis** for {{research_topic}}.
|
|
156
|
-
|
|
157
|
-
**Key Industry Findings:**
|
|
158
|
-
|
|
159
|
-
- Market size and valuation thoroughly analyzed
|
|
160
|
-
- Growth dynamics and market structure documented
|
|
161
|
-
- Industry trends and evolution patterns identified
|
|
162
|
-
- Competitive dynamics clearly mapped
|
|
163
|
-
- Multiple sources verified for critical insights
|
|
164
|
-
|
|
165
|
-
**Ready to proceed to competitive landscape analysis?**
|
|
166
|
-
[C] Continue - Save this to document and proceed to competitive landscape
|
|
167
|
-
|
|
168
|
-
### 6. Handle Continue Selection
|
|
169
|
-
|
|
170
|
-
#### If 'C' (Continue):
|
|
171
|
-
|
|
172
|
-
- **CONTENT ALREADY WRITTEN TO DOCUMENT**
|
|
173
|
-
- Update frontmatter: `stepsCompleted: [1, 2]`
|
|
174
|
-
- Load: `./step-03-competitive-landscape.md`
|
|
175
|
-
|
|
176
|
-
## APPEND TO DOCUMENT:
|
|
177
|
-
|
|
178
|
-
Content is already written to document when generated in step 4. No additional append needed.
|
|
179
|
-
|
|
180
|
-
## SUCCESS METRICS:
|
|
181
|
-
|
|
182
|
-
✅ Market size and valuation thoroughly analyzed
|
|
183
|
-
✅ Growth dynamics and market structure documented
|
|
184
|
-
✅ Industry trends and evolution patterns identified
|
|
185
|
-
✅ Competitive dynamics clearly mapped
|
|
186
|
-
✅ Multiple sources verified for critical insights
|
|
187
|
-
✅ Content written immediately to document
|
|
188
|
-
✅ [C] continue option presented and handled correctly
|
|
189
|
-
✅ Proper routing to next step (competitive landscape)
|
|
190
|
-
✅ Research goals alignment maintained
|
|
191
|
-
|
|
192
|
-
## FAILURE MODES:
|
|
193
|
-
|
|
194
|
-
❌ Relying on training data instead of web search for current facts
|
|
195
|
-
❌ Missing critical market size or growth data
|
|
196
|
-
❌ Incomplete market structure analysis
|
|
197
|
-
❌ Not identifying key industry trends
|
|
198
|
-
❌ Not writing content immediately to document
|
|
199
|
-
❌ Not presenting [C] continue option after content generation
|
|
200
|
-
❌ Not routing to competitive landscape step
|
|
201
|
-
|
|
202
|
-
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
|
|
203
|
-
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
|
204
|
-
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
|
205
|
-
|
|
206
|
-
## INDUSTRY RESEARCH PROTOCOLS:
|
|
207
|
-
|
|
208
|
-
- Research market research reports and industry analyses
|
|
209
|
-
- Use authoritative sources (market research firms, industry associations)
|
|
210
|
-
- Analyze market size, growth rates, and segmentation data
|
|
211
|
-
- Study industry trends and evolution patterns
|
|
212
|
-
- Search the web to verify facts
|
|
213
|
-
- Present conflicting information when sources disagree
|
|
214
|
-
- Apply confidence levels appropriately
|
|
215
|
-
|
|
216
|
-
## INDUSTRY ANALYSIS STANDARDS:
|
|
217
|
-
|
|
218
|
-
- Always cite URLs for web search results
|
|
219
|
-
- Use authoritative industry research sources
|
|
220
|
-
- Note data currency and potential limitations
|
|
221
|
-
- Present multiple perspectives when sources conflict
|
|
222
|
-
- Apply confidence levels to uncertain data
|
|
223
|
-
- Focus on actionable industry insights
|
|
224
|
-
|
|
225
|
-
## NEXT STEP:
|
|
226
|
-
|
|
227
|
-
After user selects 'C', load `./step-03-competitive-landscape.md` to analyze competitive landscape, key players, and ecosystem analysis for {{research_topic}}.
|
|
228
|
-
|
|
229
|
-
Remember: Always write research content to document immediately and search the web to verify facts!
|