bmad-method 6.1.1-next.0 → 6.1.1-next.10
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/AGENTS.md +9 -0
- package/package.json +2 -1
- package/src/bmm/agents/analyst.agent.yaml +2 -2
- package/src/bmm/agents/architect.agent.yaml +2 -2
- package/src/bmm/agents/dev.agent.yaml +1 -1
- package/src/bmm/agents/pm.agent.yaml +1 -1
- package/src/bmm/agents/quick-flow-solo-dev.agent.yaml +1 -1
- package/src/bmm/agents/sm.agent.yaml +1 -1
- package/src/bmm/agents/ux-designer.agent.yaml +1 -1
- package/src/bmm/module-help.csv +9 -9
- package/src/bmm/workflows/1-analysis/bmad-create-product-brief/SKILL.md +6 -0
- package/src/bmm/workflows/1-analysis/bmad-create-product-brief/bmad-skill-manifest.yaml +1 -0
- package/src/bmm/workflows/1-analysis/{create-product-brief → bmad-create-product-brief}/steps/step-01-init.md +2 -2
- package/src/bmm/workflows/1-analysis/{create-product-brief → bmad-create-product-brief}/steps/step-01b-continue.md +3 -3
- package/src/bmm/workflows/1-analysis/{create-product-brief → bmad-create-product-brief}/steps/step-02-vision.md +1 -1
- package/src/bmm/workflows/1-analysis/{create-product-brief → bmad-create-product-brief}/steps/step-03-users.md +1 -1
- package/src/bmm/workflows/1-analysis/{create-product-brief → bmad-create-product-brief}/steps/step-04-metrics.md +1 -1
- package/src/bmm/workflows/1-analysis/{create-product-brief → bmad-create-product-brief}/steps/step-05-scope.md +1 -1
- package/src/bmm/workflows/1-analysis/{create-product-brief → bmad-create-product-brief}/workflow.md +1 -6
- package/src/bmm/workflows/1-analysis/research/bmad-domain-research/SKILL.md +6 -0
- package/src/bmm/workflows/1-analysis/research/bmad-domain-research/bmad-skill-manifest.yaml +1 -0
- package/src/bmm/workflows/1-analysis/research/{domain-steps → bmad-domain-research/domain-steps}/step-01-init.md +2 -2
- package/src/bmm/workflows/1-analysis/research/{domain-steps → bmad-domain-research/domain-steps}/step-02-domain-analysis.md +2 -2
- package/src/bmm/workflows/1-analysis/research/{domain-steps → bmad-domain-research/domain-steps}/step-03-competitive-landscape.md +2 -2
- package/src/bmm/workflows/1-analysis/research/{domain-steps → bmad-domain-research/domain-steps}/step-04-regulatory-focus.md +2 -2
- package/src/bmm/workflows/1-analysis/research/{domain-steps → bmad-domain-research/domain-steps}/step-05-technical-trends.md +1 -1
- package/src/bmm/workflows/1-analysis/research/bmad-domain-research/research.template.md +29 -0
- package/src/bmm/workflows/1-analysis/research/{workflow-domain-research.md → bmad-domain-research/workflow.md} +0 -5
- package/src/bmm/workflows/1-analysis/research/bmad-skill-manifest.yaml +0 -5
- package/src/bmm/workflows/2-plan-workflows/bmad-create-ux-design/SKILL.md +6 -0
- package/src/bmm/workflows/2-plan-workflows/bmad-create-ux-design/bmad-skill-manifest.yaml +1 -0
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-01-init.md +2 -2
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-01b-continue.md +3 -3
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-02-discovery.md +2 -2
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-03-core-experience.md +2 -2
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-04-emotional-response.md +2 -2
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-05-inspiration.md +2 -2
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-06-design-system.md +2 -2
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-07-defining-experience.md +2 -2
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-08-visual-foundation.md +2 -2
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-09-design-directions.md +2 -2
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-10-user-journeys.md +2 -2
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-11-component-strategy.md +2 -2
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-12-ux-patterns.md +2 -2
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-13-responsive-accessibility.md +2 -2
- package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/workflow.md +2 -7
- package/src/bmm/workflows/3-solutioning/bmad-check-implementation-readiness/SKILL.md +6 -0
- package/src/bmm/workflows/3-solutioning/bmad-check-implementation-readiness/bmad-skill-manifest.yaml +1 -0
- package/src/bmm/workflows/3-solutioning/{check-implementation-readiness → bmad-check-implementation-readiness}/workflow.md +0 -5
- package/src/bmm/workflows/3-solutioning/bmad-create-architecture/SKILL.md +6 -0
- package/src/bmm/workflows/3-solutioning/bmad-create-architecture/bmad-skill-manifest.yaml +1 -0
- package/src/bmm/workflows/3-solutioning/{create-architecture → bmad-create-architecture}/steps/step-01-init.md +2 -2
- package/src/bmm/workflows/3-solutioning/{create-architecture → bmad-create-architecture}/steps/step-01b-continue.md +9 -9
- package/src/bmm/workflows/3-solutioning/{create-architecture → bmad-create-architecture}/steps/step-02-context.md +2 -2
- package/src/bmm/workflows/3-solutioning/{create-architecture → bmad-create-architecture}/steps/step-03-starter.md +2 -2
- package/src/bmm/workflows/3-solutioning/{create-architecture → bmad-create-architecture}/steps/step-04-decisions.md +2 -2
- package/src/bmm/workflows/3-solutioning/{create-architecture → bmad-create-architecture}/steps/step-05-patterns.md +2 -2
- package/src/bmm/workflows/3-solutioning/{create-architecture → bmad-create-architecture}/steps/step-06-structure.md +2 -2
- package/src/bmm/workflows/3-solutioning/{create-architecture → bmad-create-architecture}/steps/step-07-validation.md +2 -2
- package/src/bmm/workflows/3-solutioning/{create-architecture → bmad-create-architecture}/workflow.md +2 -7
- package/src/bmm/workflows/4-implementation/bmad-create-story/SKILL.md +6 -0
- package/src/bmm/workflows/4-implementation/bmad-create-story/bmad-skill-manifest.yaml +1 -0
- package/src/bmm/workflows/4-implementation/{create-story → bmad-create-story}/workflow.md +4 -4
- package/src/bmm/workflows/4-implementation/bmad-dev-story/SKILL.md +6 -0
- package/src/bmm/workflows/4-implementation/bmad-dev-story/bmad-skill-manifest.yaml +1 -0
- package/src/bmm/workflows/4-implementation/{dev-story → bmad-dev-story}/workflow.md +1 -7
- package/src/bmm/workflows/bmad-quick-flow/bmad-quick-dev/SKILL.md +6 -0
- package/src/bmm/workflows/bmad-quick-flow/bmad-quick-dev/bmad-skill-manifest.yaml +1 -0
- package/src/bmm/workflows/bmad-quick-flow/{quick-dev → bmad-quick-dev}/steps/step-01-mode-detection.md +6 -6
- package/src/bmm/workflows/bmad-quick-flow/{quick-dev → bmad-quick-dev}/steps/step-02-context-gathering.md +1 -1
- package/src/bmm/workflows/bmad-quick-flow/{quick-dev → bmad-quick-dev}/steps/step-03-execute.md +1 -1
- package/src/bmm/workflows/bmad-quick-flow/{quick-dev → bmad-quick-dev}/steps/step-04-self-check.md +1 -1
- package/src/bmm/workflows/bmad-quick-flow/{quick-dev → bmad-quick-dev}/steps/step-05-adversarial-review.md +1 -1
- package/src/bmm/workflows/bmad-quick-flow/{quick-dev → bmad-quick-dev}/workflow.md +2 -8
- package/src/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-04-review.md +1 -1
- package/src/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md +0 -1
- package/src/core/tasks/bmad-advanced-elicitation/workflow.md +0 -2
- package/tools/cli/installers/lib/modules/manager.js +1 -1
- package/src/bmm/workflows/1-analysis/create-product-brief/bmad-skill-manifest.yaml +0 -3
- package/src/bmm/workflows/2-plan-workflows/create-ux-design/bmad-skill-manifest.yaml +0 -3
- package/src/bmm/workflows/3-solutioning/check-implementation-readiness/bmad-skill-manifest.yaml +0 -3
- package/src/bmm/workflows/3-solutioning/create-architecture/bmad-skill-manifest.yaml +0 -3
- package/src/bmm/workflows/4-implementation/create-story/bmad-skill-manifest.yaml +0 -3
- package/src/bmm/workflows/4-implementation/dev-story/bmad-skill-manifest.yaml +0 -3
- package/src/bmm/workflows/bmad-quick-flow/quick-dev/bmad-skill-manifest.yaml +0 -3
- /package/src/bmm/workflows/1-analysis/{create-product-brief → bmad-create-product-brief}/product-brief.template.md +0 -0
- /package/src/bmm/workflows/1-analysis/{create-product-brief → bmad-create-product-brief}/steps/step-06-complete.md +0 -0
- /package/src/bmm/workflows/1-analysis/research/{domain-steps → bmad-domain-research/domain-steps}/step-06-research-synthesis.md +0 -0
- /package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/steps/step-14-complete.md +0 -0
- /package/src/bmm/workflows/2-plan-workflows/{create-ux-design → bmad-create-ux-design}/ux-design-template.md +0 -0
- /package/src/bmm/workflows/3-solutioning/{check-implementation-readiness → bmad-check-implementation-readiness}/steps/step-01-document-discovery.md +0 -0
- /package/src/bmm/workflows/3-solutioning/{check-implementation-readiness → bmad-check-implementation-readiness}/steps/step-02-prd-analysis.md +0 -0
- /package/src/bmm/workflows/3-solutioning/{check-implementation-readiness → bmad-check-implementation-readiness}/steps/step-03-epic-coverage-validation.md +0 -0
- /package/src/bmm/workflows/3-solutioning/{check-implementation-readiness → bmad-check-implementation-readiness}/steps/step-04-ux-alignment.md +0 -0
- /package/src/bmm/workflows/3-solutioning/{check-implementation-readiness → bmad-check-implementation-readiness}/steps/step-05-epic-quality-review.md +0 -0
- /package/src/bmm/workflows/3-solutioning/{check-implementation-readiness → bmad-check-implementation-readiness}/steps/step-06-final-assessment.md +0 -0
- /package/src/bmm/workflows/3-solutioning/{check-implementation-readiness → bmad-check-implementation-readiness}/templates/readiness-report-template.md +0 -0
- /package/src/bmm/workflows/3-solutioning/{create-architecture → bmad-create-architecture}/architecture-decision-template.md +0 -0
- /package/src/bmm/workflows/3-solutioning/{create-architecture → bmad-create-architecture}/data/domain-complexity.csv +0 -0
- /package/src/bmm/workflows/3-solutioning/{create-architecture → bmad-create-architecture}/data/project-types.csv +0 -0
- /package/src/bmm/workflows/3-solutioning/{create-architecture → bmad-create-architecture}/steps/step-08-complete.md +0 -0
- /package/src/bmm/workflows/4-implementation/{create-story → bmad-create-story}/checklist.md +0 -0
- /package/src/bmm/workflows/4-implementation/{create-story → bmad-create-story}/discover-inputs.md +0 -0
- /package/src/bmm/workflows/4-implementation/{create-story → bmad-create-story}/template.md +0 -0
- /package/src/bmm/workflows/4-implementation/{dev-story → bmad-dev-story}/checklist.md +0 -0
- /package/src/bmm/workflows/bmad-quick-flow/{quick-dev → bmad-quick-dev}/steps/step-06-resolve-findings.md +0 -0
package/AGENTS.md
ADDED
|
@@ -0,0 +1,9 @@
|
|
|
1
|
+
# BMAD-METHOD
|
|
2
|
+
|
|
3
|
+
Open source framework for structured, agent-assisted software delivery.
|
|
4
|
+
|
|
5
|
+
## Rules
|
|
6
|
+
|
|
7
|
+
- Use Conventional Commits for every commit.
|
|
8
|
+
- Before pushing, run `npm ci && npm run quality` on `HEAD` in the exact checkout you are about to push.
|
|
9
|
+
`quality` mirrors the checks in `.github/workflows/quality.yaml`.
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"$schema": "https://json.schemastore.org/package.json",
|
|
3
3
|
"name": "bmad-method",
|
|
4
|
-
"version": "6.1.1-next.
|
|
4
|
+
"version": "6.1.1-next.10",
|
|
5
5
|
"description": "Breakthrough Method of Agile AI-driven Development",
|
|
6
6
|
"keywords": [
|
|
7
7
|
"agile",
|
|
@@ -39,6 +39,7 @@
|
|
|
39
39
|
"lint:fix": "eslint . --ext .js,.cjs,.mjs,.yaml --fix",
|
|
40
40
|
"lint:md": "markdownlint-cli2 \"**/*.md\"",
|
|
41
41
|
"prepare": "command -v husky >/dev/null 2>&1 && husky || exit 0",
|
|
42
|
+
"quality": "npm run format:check && npm run lint && npm run lint:md && npm run docs:build && npm run validate:schemas && npm run test:schemas && npm run test:install && npm run validate:refs",
|
|
42
43
|
"rebundle": "node tools/cli/bundlers/bundle-web.js rebundle",
|
|
43
44
|
"test": "npm run test:schemas && npm run test:refs && npm run test:install && npm run validate:schemas && npm run lint && npm run lint:md && npm run format:check",
|
|
44
45
|
"test:coverage": "c8 --reporter=text --reporter=html npm run test:schemas",
|
|
@@ -27,7 +27,7 @@ agent:
|
|
|
27
27
|
description: "[MR] Market Research: Market analysis, competitive landscape, customer needs and trends"
|
|
28
28
|
|
|
29
29
|
- trigger: DR or fuzzy match on domain-research
|
|
30
|
-
exec: "
|
|
30
|
+
exec: "skill:bmad-domain-research"
|
|
31
31
|
description: "[DR] Domain Research: Industry domain deep dive, subject matter expertise and terminology"
|
|
32
32
|
|
|
33
33
|
- trigger: TR or fuzzy match on technical-research
|
|
@@ -35,7 +35,7 @@ agent:
|
|
|
35
35
|
description: "[TR] Technical Research: Technical feasibility, architecture options and implementation approaches"
|
|
36
36
|
|
|
37
37
|
- trigger: CB or fuzzy match on product-brief
|
|
38
|
-
exec: "
|
|
38
|
+
exec: "skill:bmad-create-product-brief"
|
|
39
39
|
description: "[CB] Create Brief: A guided experience to nail down your product idea into an executive brief"
|
|
40
40
|
|
|
41
41
|
- trigger: DP or fuzzy match on document-project
|
|
@@ -21,9 +21,9 @@ agent:
|
|
|
21
21
|
|
|
22
22
|
menu:
|
|
23
23
|
- trigger: CA or fuzzy match on create-architecture
|
|
24
|
-
exec: "
|
|
24
|
+
exec: "skill:bmad-create-architecture"
|
|
25
25
|
description: "[CA] Create Architecture: Guided Workflow to document technical decisions to keep implementation on track"
|
|
26
26
|
|
|
27
27
|
- trigger: IR or fuzzy match on implementation-readiness
|
|
28
|
-
exec: "
|
|
28
|
+
exec: "skill:bmad-check-implementation-readiness"
|
|
29
29
|
description: "[IR] Implementation Readiness: Ensure the PRD, UX, and Architecture and Epics and Stories List are all aligned"
|
|
@@ -30,7 +30,7 @@ agent:
|
|
|
30
30
|
|
|
31
31
|
menu:
|
|
32
32
|
- trigger: DS or fuzzy match on dev-story
|
|
33
|
-
exec: "
|
|
33
|
+
exec: "skill:bmad-dev-story"
|
|
34
34
|
description: "[DS] Dev Story: Write the next or specified stories tests and code."
|
|
35
35
|
|
|
36
36
|
- trigger: CR or fuzzy match on code-review
|
|
@@ -36,7 +36,7 @@ agent:
|
|
|
36
36
|
description: "[CE] Create Epics and Stories: Create the Epics and Stories Listing, these are the specs that will drive development"
|
|
37
37
|
|
|
38
38
|
- trigger: IR or fuzzy match on implementation-readiness
|
|
39
|
-
exec: "
|
|
39
|
+
exec: "skill:bmad-check-implementation-readiness"
|
|
40
40
|
description: "[IR] Implementation Readiness: Ensure the PRD, UX, and Architecture and Epics and Stories List are all aligned"
|
|
41
41
|
|
|
42
42
|
- trigger: CC or fuzzy match on correct-course
|
|
@@ -24,7 +24,7 @@ agent:
|
|
|
24
24
|
description: "[QS] Quick Spec: Architect a quick but complete technical spec with implementation-ready stories/specs"
|
|
25
25
|
|
|
26
26
|
- trigger: QD or fuzzy match on quick-dev
|
|
27
|
-
exec: "
|
|
27
|
+
exec: "skill:bmad-quick-dev"
|
|
28
28
|
description: "[QD] Quick-flow Develop: Implement a story tech spec end-to-end (Core of Quick Flow)"
|
|
29
29
|
|
|
30
30
|
- trigger: QQ or fuzzy match on bmad-quick-dev-new-preview
|
|
@@ -24,7 +24,7 @@ agent:
|
|
|
24
24
|
description: "[SP] Sprint Planning: Generate or update the record that will sequence the tasks to complete the full project that the dev agent will follow"
|
|
25
25
|
|
|
26
26
|
- trigger: CS or fuzzy match on create-story
|
|
27
|
-
exec: "
|
|
27
|
+
exec: "skill:bmad-create-story"
|
|
28
28
|
description: "[CS] Context Story: Prepare a story with all required context for implementation for the developer agent"
|
|
29
29
|
|
|
30
30
|
- trigger: ER or fuzzy match on epic-retrospective
|
|
@@ -23,5 +23,5 @@ agent:
|
|
|
23
23
|
|
|
24
24
|
menu:
|
|
25
25
|
- trigger: CU or fuzzy match on ux-design
|
|
26
|
-
exec: "
|
|
26
|
+
exec: "skill:bmad-create-ux-design"
|
|
27
27
|
description: "[CU] Create UX: Guidance through realizing the plan for your UX to inform architecture and implementation. Provides more details than what was discovered in the PRD"
|
package/src/bmm/module-help.csv
CHANGED
|
@@ -2,7 +2,7 @@ module,phase,name,code,sequence,workflow-file,command,required,agent,options,des
|
|
|
2
2
|
bmm,anytime,Document Project,DP,,_bmad/bmm/workflows/document-project/workflow.md,bmad-bmm-document-project,false,analyst,Create Mode,"Analyze an existing project to produce useful documentation",project-knowledge,*,
|
|
3
3
|
bmm,anytime,Generate Project Context,GPC,,_bmad/bmm/workflows/generate-project-context/workflow.md,bmad-bmm-generate-project-context,false,analyst,Create Mode,"Scan existing codebase to generate a lean LLM-optimized project-context.md containing critical implementation rules patterns and conventions for AI agents. Essential for brownfield projects and quick-flow.",output_folder,"project context",
|
|
4
4
|
bmm,anytime,Quick Spec,QS,,_bmad/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md,bmad-bmm-quick-spec,false,quick-flow-solo-dev,Create Mode,"Do not suggest for potentially very complex things unless requested or if the user complains that they do not want to follow the extensive planning of the bmad method. Quick one-off tasks small changes simple apps brownfield additions to well established patterns utilities without extensive planning",planning_artifacts,"tech spec",
|
|
5
|
-
bmm,anytime,Quick Dev,QD,,
|
|
5
|
+
bmm,anytime,Quick Dev,QD,,skill:bmad-quick-dev,bmad-bmm-quick-dev,false,quick-flow-solo-dev,Create Mode,"Quick one-off tasks small changes simple apps utilities without extensive planning - Do not suggest for potentially very complex things unless requested or if the user complains that they do not want to follow the extensive planning of the bmad method, unless the user is already working through the implementation phase and just requests a 1 off things not already in the plan",,,
|
|
6
6
|
bmm,anytime,Quick Dev New Preview,QQ,,skill:bmad-quick-dev-new-preview,bmad-bmm-quick-dev-new-preview,false,quick-flow-solo-dev,Create Mode,"Unified quick flow (experimental): clarify intent plan implement review and present in a single workflow",implementation_artifacts,"tech spec implementation",
|
|
7
7
|
bmm,anytime,Correct Course,CC,,_bmad/bmm/workflows/4-implementation/correct-course/workflow.md,bmad-bmm-correct-course,false,sm,Create Mode,"Anytime: Navigate significant changes. May recommend start over update PRD redo architecture sprint planning or correct epics and stories",planning_artifacts,"change proposal",
|
|
8
8
|
bmm,anytime,Write Document,WD,,_bmad/bmm/agents/tech-writer/tech-writer.agent.yaml,,false,tech-writer,,"Describe in detail what you want, and the agent will follow the documentation best practices defined in agent memory. Multi-turn conversation with subprocess for research/review.",project-knowledge,"document",
|
|
@@ -12,21 +12,21 @@ bmm,anytime,Validate Document,VD,,_bmad/bmm/agents/tech-writer/tech-writer.agent
|
|
|
12
12
|
bmm,anytime,Explain Concept,EC,,_bmad/bmm/agents/tech-writer/tech-writer.agent.yaml,,false,tech-writer,,"Create clear technical explanations with examples and diagrams for complex concepts. Breaks down into digestible sections using task-oriented approach.",project_knowledge,"explanation",
|
|
13
13
|
bmm,1-analysis,Brainstorm Project,BP,10,skill:bmad-brainstorming,bmad-brainstorming,false,analyst,data=_bmad/bmm/data/project-context-template.md,"Expert Guided Facilitation through a single or multiple techniques",planning_artifacts,"brainstorming session",
|
|
14
14
|
bmm,1-analysis,Market Research,MR,20,_bmad/bmm/workflows/1-analysis/research/workflow-market-research.md,bmad-bmm-market-research,false,analyst,Create Mode,"Market analysis competitive landscape customer needs and trends","planning_artifacts|project-knowledge","research documents",
|
|
15
|
-
bmm,1-analysis,Domain Research,DR,21,
|
|
15
|
+
bmm,1-analysis,Domain Research,DR,21,skill:bmad-domain-research,bmad-bmm-domain-research,false,analyst,Create Mode,"Industry domain deep dive subject matter expertise and terminology","planning_artifacts|project_knowledge","research documents",
|
|
16
16
|
bmm,1-analysis,Technical Research,TR,22,_bmad/bmm/workflows/1-analysis/research/workflow-technical-research.md,bmad-bmm-technical-research,false,analyst,Create Mode,"Technical feasibility architecture options and implementation approaches","planning_artifacts|project_knowledge","research documents",
|
|
17
|
-
bmm,1-analysis,Create Brief,CB,30,
|
|
17
|
+
bmm,1-analysis,Create Brief,CB,30,skill:bmad-create-product-brief,bmad-bmm-create-product-brief,false,analyst,Create Mode,"A guided experience to nail down your product idea",planning_artifacts,"product brief",
|
|
18
18
|
bmm,2-planning,Create PRD,CP,10,_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-create-prd.md,bmad-bmm-create-prd,true,pm,Create Mode,"Expert led facilitation to produce your Product Requirements Document",planning_artifacts,prd,
|
|
19
19
|
bmm,2-planning,Validate PRD,VP,20,_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-validate-prd.md,bmad-bmm-validate-prd,false,pm,Validate Mode,"Validate PRD is comprehensive lean well organized and cohesive",planning_artifacts,"prd validation report",
|
|
20
20
|
bmm,2-planning,Edit PRD,EP,25,_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-edit-prd.md,bmad-bmm-edit-prd,false,pm,Edit Mode,"Improve and enhance an existing PRD",planning_artifacts,"updated prd",
|
|
21
|
-
bmm,2-planning,Create UX,CU,30,
|
|
22
|
-
bmm,3-solutioning,Create Architecture,CA,10,
|
|
21
|
+
bmm,2-planning,Create UX,CU,30,skill:bmad-create-ux-design,bmad-bmm-create-ux-design,false,ux-designer,Create Mode,"Guidance through realizing the plan for your UX, strongly recommended if a UI is a primary piece of the proposed project",planning_artifacts,"ux design",
|
|
22
|
+
bmm,3-solutioning,Create Architecture,CA,10,skill:bmad-create-architecture,bmad-bmm-create-architecture,true,architect,Create Mode,"Guided Workflow to document technical decisions",planning_artifacts,architecture,
|
|
23
23
|
bmm,3-solutioning,Create Epics and Stories,CE,30,_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md,bmad-bmm-create-epics-and-stories,true,pm,Create Mode,"Create the Epics and Stories Listing",planning_artifacts,"epics and stories",
|
|
24
|
-
bmm,3-solutioning,Check Implementation Readiness,IR,70,
|
|
24
|
+
bmm,3-solutioning,Check Implementation Readiness,IR,70,skill:bmad-check-implementation-readiness,bmad-bmm-check-implementation-readiness,true,architect,Validate Mode,"Ensure PRD UX Architecture and Epics Stories are aligned",planning_artifacts,"readiness report",
|
|
25
25
|
bmm,4-implementation,Sprint Planning,SP,10,_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.md,bmad-bmm-sprint-planning,true,sm,Create Mode,"Generate sprint plan for development tasks - this kicks off the implementation phase by producing a plan the implementation agents will follow in sequence for every story in the plan.",implementation_artifacts,"sprint status",
|
|
26
26
|
bmm,4-implementation,Sprint Status,SS,20,_bmad/bmm/workflows/4-implementation/sprint-status/workflow.md,bmad-bmm-sprint-status,false,sm,Create Mode,"Anytime: Summarize sprint status and route to next workflow",,,
|
|
27
|
-
bmm,4-implementation,Validate Story,VS,35,
|
|
28
|
-
bmm,4-implementation,Create Story,CS,30,
|
|
29
|
-
bmm,4-implementation,Dev Story,DS,40,
|
|
27
|
+
bmm,4-implementation,Validate Story,VS,35,skill:bmad-create-story,bmad-bmm-create-story,false,sm,Validate Mode,"Validates story readiness and completeness before development work begins",implementation_artifacts,"story validation report",
|
|
28
|
+
bmm,4-implementation,Create Story,CS,30,skill:bmad-create-story,bmad-bmm-create-story,true,sm,Create Mode,"Story cycle start: Prepare first found story in the sprint plan that is next, or if the command is run with a specific epic and story designation with context. Once complete, then VS then DS then CR then back to DS if needed or next CS or ER",implementation_artifacts,story,
|
|
29
|
+
bmm,4-implementation,Dev Story,DS,40,skill:bmad-dev-story,bmad-bmm-dev-story,true,dev,Create Mode,"Story cycle: Execute story implementation tasks and tests then CR then back to DS if fixes needed",,,
|
|
30
30
|
bmm,4-implementation,Code Review,CR,50,_bmad/bmm/workflows/4-implementation/code-review/workflow.md,bmad-bmm-code-review,false,dev,Create Mode,"Story cycle: If issues back to DS if approved then next CS or ER if epic complete",,,
|
|
31
31
|
bmm,4-implementation,QA Automation Test,QA,45,_bmad/bmm/workflows/qa-generate-e2e-tests/workflow.md,bmad-bmm-qa-automate,false,qa,Create Mode,"Generate automated API and E2E tests for implemented code using the project's existing test framework (detects existing well known in use test frameworks). Use after implementation to add test coverage. NOT for code review or story validation - use CR for that.",implementation_artifacts,"test suite",
|
|
32
32
|
bmm,4-implementation,Retrospective,ER,60,_bmad/bmm/workflows/4-implementation/retrospective/workflow.md,bmad-bmm-retrospective,false,sm,Create Mode,"Optional at epic end: Review completed work lessons learned and next epic or if major issues consider CC",implementation_artifacts,retrospective,
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
type: skill
|
|
@@ -3,7 +3,7 @@ name: 'step-01-init'
|
|
|
3
3
|
description: 'Initialize the product brief workflow by detecting continuation state and setting up the document'
|
|
4
4
|
|
|
5
5
|
# File References
|
|
6
|
-
nextStepFile: '
|
|
6
|
+
nextStepFile: './step-02-vision.md'
|
|
7
7
|
outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
|
|
8
8
|
|
|
9
9
|
# Template References
|
|
@@ -73,7 +73,7 @@ If the document exists and has frontmatter with `stepsCompleted`:
|
|
|
73
73
|
|
|
74
74
|
**Continuation Protocol:**
|
|
75
75
|
|
|
76
|
-
- **STOP immediately** and load
|
|
76
|
+
- **STOP immediately** and load `./step-01b-continue.md`
|
|
77
77
|
- Do not proceed with any initialization tasks
|
|
78
78
|
- Let step-01b handle all continuation logic
|
|
79
79
|
- This is an auto-proceed situation - no user choice needed
|
|
@@ -95,9 +95,9 @@ Does this look right, or do you want to make any adjustments before we proceed?"
|
|
|
95
95
|
**Next Step Logic:**
|
|
96
96
|
Based on `lastStep` value, determine which step to load next:
|
|
97
97
|
|
|
98
|
-
- If `lastStep = 1` → Load
|
|
99
|
-
- If `lastStep = 2` → Load
|
|
100
|
-
- If `lastStep = 3` → Load
|
|
98
|
+
- If `lastStep = 1` → Load `./step-02-vision.md`
|
|
99
|
+
- If `lastStep = 2` → Load `./step-03-users.md`
|
|
100
|
+
- If `lastStep = 3` → Load `./step-04-metrics.md`
|
|
101
101
|
- Continue this pattern for all steps
|
|
102
102
|
- If `lastStep = 6` → Workflow already complete
|
|
103
103
|
|
|
@@ -3,7 +3,7 @@ name: 'step-02-vision'
|
|
|
3
3
|
description: 'Discover and define the core product vision, problem statement, and unique value proposition'
|
|
4
4
|
|
|
5
5
|
# File References
|
|
6
|
-
nextStepFile: '
|
|
6
|
+
nextStepFile: './step-03-users.md'
|
|
7
7
|
outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
|
|
8
8
|
|
|
9
9
|
# Task References
|
|
@@ -3,7 +3,7 @@ name: 'step-03-users'
|
|
|
3
3
|
description: 'Define target users with rich personas and map their key interactions with the product'
|
|
4
4
|
|
|
5
5
|
# File References
|
|
6
|
-
nextStepFile: '
|
|
6
|
+
nextStepFile: './step-04-metrics.md'
|
|
7
7
|
outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
|
|
8
8
|
|
|
9
9
|
# Task References
|
|
@@ -3,7 +3,7 @@ name: 'step-04-metrics'
|
|
|
3
3
|
description: 'Define comprehensive success metrics that include user success, business objectives, and key performance indicators'
|
|
4
4
|
|
|
5
5
|
# File References
|
|
6
|
-
nextStepFile: '
|
|
6
|
+
nextStepFile: './step-05-scope.md'
|
|
7
7
|
outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
|
|
8
8
|
|
|
9
9
|
# Task References
|
|
@@ -3,7 +3,7 @@ name: 'step-05-scope'
|
|
|
3
3
|
description: 'Define MVP scope with clear boundaries and outline future vision while managing scope creep'
|
|
4
4
|
|
|
5
5
|
# File References
|
|
6
|
-
nextStepFile: '
|
|
6
|
+
nextStepFile: './step-06-complete.md'
|
|
7
7
|
outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
|
|
8
8
|
|
|
9
9
|
# Task References
|
package/src/bmm/workflows/1-analysis/{create-product-brief → bmad-create-product-brief}/workflow.md
RENAMED
|
@@ -1,8 +1,3 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: create-product-brief
|
|
3
|
-
description: 'Create product brief through collaborative discovery. Use when the user says "lets create a product brief" or "help me create a project brief"'
|
|
4
|
-
---
|
|
5
|
-
|
|
6
1
|
# Product Brief Workflow
|
|
7
2
|
|
|
8
3
|
**Goal:** Create comprehensive product briefs through collaborative step-by-step discovery as creative Business Analyst working with the user as peers.
|
|
@@ -54,4 +49,4 @@ Load and read full config from {project-root}/_bmad/bmm/config.yaml and resolve:
|
|
|
54
49
|
|
|
55
50
|
### 2. First Step EXECUTION
|
|
56
51
|
|
|
57
|
-
Read fully and follow:
|
|
52
|
+
Read fully and follow: `./steps/step-01-init.md` to begin the workflow.
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
type: skill
|
|
@@ -78,7 +78,7 @@ For **{{research_topic}}**, I will research:
|
|
|
78
78
|
|
|
79
79
|
- Document scope confirmation in research file
|
|
80
80
|
- Update frontmatter: `stepsCompleted: [1]`
|
|
81
|
-
- Load:
|
|
81
|
+
- Load: `./step-02-domain-analysis.md`
|
|
82
82
|
|
|
83
83
|
## APPEND TO DOCUMENT:
|
|
84
84
|
|
|
@@ -132,6 +132,6 @@ When user selects 'C', append scope confirmation:
|
|
|
132
132
|
|
|
133
133
|
## NEXT STEP:
|
|
134
134
|
|
|
135
|
-
After user selects 'C', load
|
|
135
|
+
After user selects 'C', load `./step-02-domain-analysis.md` to begin industry analysis.
|
|
136
136
|
|
|
137
137
|
Remember: This is SCOPE CONFIRMATION ONLY - no actual domain research yet, just confirming the research approach and scope!
|
|
@@ -171,7 +171,7 @@ _Source: [URL]_
|
|
|
171
171
|
|
|
172
172
|
- **CONTENT ALREADY WRITTEN TO DOCUMENT**
|
|
173
173
|
- Update frontmatter: `stepsCompleted: [1, 2]`
|
|
174
|
-
- Load:
|
|
174
|
+
- Load: `./step-03-competitive-landscape.md`
|
|
175
175
|
|
|
176
176
|
## APPEND TO DOCUMENT:
|
|
177
177
|
|
|
@@ -224,6 +224,6 @@ Content is already written to document when generated in step 4. No additional a
|
|
|
224
224
|
|
|
225
225
|
## NEXT STEP:
|
|
226
226
|
|
|
227
|
-
After user selects 'C', load
|
|
227
|
+
After user selects 'C', load `./step-03-competitive-landscape.md` to analyze competitive landscape, key players, and ecosystem analysis for {{research_topic}}.
|
|
228
228
|
|
|
229
229
|
Remember: Always write research content to document immediately and search the web to verify facts!
|
|
@@ -180,7 +180,7 @@ _Source: [URL]_
|
|
|
180
180
|
|
|
181
181
|
- **CONTENT ALREADY WRITTEN TO DOCUMENT**
|
|
182
182
|
- Update frontmatter: `stepsCompleted: [1, 2, 3]`
|
|
183
|
-
- Load:
|
|
183
|
+
- Load: `./step-04-regulatory-focus.md`
|
|
184
184
|
|
|
185
185
|
## APPEND TO DOCUMENT:
|
|
186
186
|
|
|
@@ -233,6 +233,6 @@ Content is already written to document when generated in step 4. No additional a
|
|
|
233
233
|
|
|
234
234
|
## NEXT STEP:
|
|
235
235
|
|
|
236
|
-
After user selects 'C', load
|
|
236
|
+
After user selects 'C', load `./step-04-regulatory-focus.md` to analyze regulatory requirements, compliance frameworks, and legal considerations for {{research_topic}}.
|
|
237
237
|
|
|
238
238
|
Remember: Always write research content to document immediately and search the web to verify facts!
|
|
@@ -155,7 +155,7 @@ Show the generated regulatory analysis and present continue option:
|
|
|
155
155
|
|
|
156
156
|
- **CONTENT ALREADY WRITTEN TO DOCUMENT**
|
|
157
157
|
- Update frontmatter: `stepsCompleted: [1, 2, 3, 4]`
|
|
158
|
-
- Load:
|
|
158
|
+
- Load: `./step-05-technical-trends.md`
|
|
159
159
|
|
|
160
160
|
## APPEND TO DOCUMENT:
|
|
161
161
|
|
|
@@ -201,6 +201,6 @@ Content is already written to document when generated in step 5. No additional a
|
|
|
201
201
|
|
|
202
202
|
## NEXT STEP:
|
|
203
203
|
|
|
204
|
-
After user selects 'C' and content is saved to document, load
|
|
204
|
+
After user selects 'C' and content is saved to document, load `./step-05-technical-trends.md` to analyze technical trends and innovations in the domain.
|
|
205
205
|
|
|
206
206
|
Remember: Search the web to verify regulatory facts and provide practical implementation considerations!
|
|
@@ -174,7 +174,7 @@ Show the generated technical analysis and present complete option:
|
|
|
174
174
|
|
|
175
175
|
- **CONTENT ALREADY WRITTEN TO DOCUMENT**
|
|
176
176
|
- Update frontmatter: `stepsCompleted: [1, 2, 3, 4, 5]`
|
|
177
|
-
- Load:
|
|
177
|
+
- Load: `./step-06-research-synthesis.md`
|
|
178
178
|
|
|
179
179
|
## APPEND TO DOCUMENT:
|
|
180
180
|
|
|
@@ -0,0 +1,29 @@
|
|
|
1
|
+
---
|
|
2
|
+
stepsCompleted: []
|
|
3
|
+
inputDocuments: []
|
|
4
|
+
workflowType: 'research'
|
|
5
|
+
lastStep: 1
|
|
6
|
+
research_type: '{{research_type}}'
|
|
7
|
+
research_topic: '{{research_topic}}'
|
|
8
|
+
research_goals: '{{research_goals}}'
|
|
9
|
+
user_name: '{{user_name}}'
|
|
10
|
+
date: '{{date}}'
|
|
11
|
+
web_research_enabled: true
|
|
12
|
+
source_verification: true
|
|
13
|
+
---
|
|
14
|
+
|
|
15
|
+
# Research Report: {{research_type}}
|
|
16
|
+
|
|
17
|
+
**Date:** {{date}}
|
|
18
|
+
**Author:** {{user_name}}
|
|
19
|
+
**Research Type:** {{research_type}}
|
|
20
|
+
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
## Research Overview
|
|
24
|
+
|
|
25
|
+
[Research overview and methodology will be appended here]
|
|
26
|
+
|
|
27
|
+
---
|
|
28
|
+
|
|
29
|
+
<!-- Content will be appended sequentially through research workflow steps -->
|
|
@@ -1,8 +1,3 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: domain-research
|
|
3
|
-
description: 'Conduct domain and industry research. Use when the user says "lets create a research report on [domain or industry]"'
|
|
4
|
-
---
|
|
5
|
-
|
|
6
1
|
# Domain Research Workflow
|
|
7
2
|
|
|
8
3
|
**Goal:** Conduct comprehensive domain/industry research using current web data and verified sources to produce complete research documents with compelling narratives and proper citations.
|
|
@@ -1,8 +1,3 @@
|
|
|
1
|
-
workflow-domain-research.md:
|
|
2
|
-
canonicalId: bmad-domain-research
|
|
3
|
-
type: workflow
|
|
4
|
-
description: "Conduct domain and industry research. Use when the user says 'lets create a research report on [domain or industry]'"
|
|
5
|
-
|
|
6
1
|
workflow-market-research.md:
|
|
7
2
|
canonicalId: bmad-market-research
|
|
8
3
|
type: workflow
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
type: skill
|
|
@@ -44,7 +44,7 @@ First, check if the output document already exists:
|
|
|
44
44
|
|
|
45
45
|
If the document exists and has frontmatter with `stepsCompleted`:
|
|
46
46
|
|
|
47
|
-
- **STOP here** and load
|
|
47
|
+
- **STOP here** and load `./step-01b-continue.md` immediately
|
|
48
48
|
- Do not proceed with any initialization tasks
|
|
49
49
|
- Let step-01b handle the continuation logic
|
|
50
50
|
|
|
@@ -110,7 +110,7 @@ Do you have any other documents you'd like me to include, or shall we continue t
|
|
|
110
110
|
|
|
111
111
|
## NEXT STEP:
|
|
112
112
|
|
|
113
|
-
After user selects [C] to continue, ensure the file `{planning_artifacts}/ux-design-specification.md` has been created and saved, and then load
|
|
113
|
+
After user selects [C] to continue, ensure the file `{planning_artifacts}/ux-design-specification.md` has been created and saved, and then load `./step-02-discovery.md` to begin the UX discovery phase.
|
|
114
114
|
|
|
115
115
|
Remember: Do NOT proceed to step-02 until output file has been updated and user explicitly selects [C] to continue!
|
|
116
116
|
|
|
@@ -72,9 +72,9 @@ Does this look right, or do you want to make any adjustments before we proceed?"
|
|
|
72
72
|
|
|
73
73
|
Based on `lastStep` value, determine which step to load next:
|
|
74
74
|
|
|
75
|
-
- If `lastStep = 1` → Load
|
|
76
|
-
- If `lastStep = 2` → Load
|
|
77
|
-
- If `lastStep = 3` → Load
|
|
75
|
+
- If `lastStep = 1` → Load `./step-02-discovery.md`
|
|
76
|
+
- If `lastStep = 2` → Load `./step-03-core-experience.md`
|
|
77
|
+
- If `lastStep = 3` → Load `./step-04-emotional-response.md`
|
|
78
78
|
- Continue this pattern for all steps
|
|
79
79
|
- If `lastStep` indicates final step → Workflow already complete
|
|
80
80
|
|
|
@@ -155,11 +155,11 @@ Show the generated project understanding content and present choices:
|
|
|
155
155
|
|
|
156
156
|
- Append the final content to `{planning_artifacts}/ux-design-specification.md`
|
|
157
157
|
- Update frontmatter: `stepsCompleted: [1, 2]`
|
|
158
|
-
- Load
|
|
158
|
+
- Load `./step-03-core-experience.md`
|
|
159
159
|
|
|
160
160
|
## APPEND TO DOCUMENT:
|
|
161
161
|
|
|
162
|
-
When user selects 'C', append the content directly to the document. Only after the content is saved to document, read fully and follow:
|
|
162
|
+
When user selects 'C', append the content directly to the document. Only after the content is saved to document, read fully and follow: `./step-03-core-experience.md`.
|
|
163
163
|
|
|
164
164
|
## SUCCESS METRICS:
|
|
165
165
|
|
|
@@ -179,7 +179,7 @@ Show the generated core experience content and present choices:
|
|
|
179
179
|
|
|
180
180
|
- Append the final content to `{planning_artifacts}/ux-design-specification.md`
|
|
181
181
|
- Update frontmatter: append step to end of stepsCompleted array
|
|
182
|
-
- Load
|
|
182
|
+
- Load `./step-04-emotional-response.md`
|
|
183
183
|
|
|
184
184
|
## APPEND TO DOCUMENT:
|
|
185
185
|
|
|
@@ -211,6 +211,6 @@ When user selects 'C', append the content directly to the document using the str
|
|
|
211
211
|
|
|
212
212
|
## NEXT STEP:
|
|
213
213
|
|
|
214
|
-
After user selects 'C' and content is saved to document, load
|
|
214
|
+
After user selects 'C' and content is saved to document, load `./step-04-emotional-response.md` to define desired emotional responses.
|
|
215
215
|
|
|
216
216
|
Remember: Do NOT proceed to step-04 until user explicitly selects 'C' from the A/P/C menu and content is saved!
|
|
@@ -182,7 +182,7 @@ Show the generated emotional response content and present choices:
|
|
|
182
182
|
|
|
183
183
|
- Append the final content to `{planning_artifacts}/ux-design-specification.md`
|
|
184
184
|
- Update frontmatter: append step to end of stepsCompleted array
|
|
185
|
-
- Load
|
|
185
|
+
- Load `./step-05-inspiration.md`
|
|
186
186
|
|
|
187
187
|
## APPEND TO DOCUMENT:
|
|
188
188
|
|
|
@@ -214,6 +214,6 @@ When user selects 'C', append the content directly to the document using the str
|
|
|
214
214
|
|
|
215
215
|
## NEXT STEP:
|
|
216
216
|
|
|
217
|
-
After user selects 'C' and content is saved to document, load
|
|
217
|
+
After user selects 'C' and content is saved to document, load `./step-05-inspiration.md` to analyze UX patterns from inspiring products.
|
|
218
218
|
|
|
219
219
|
Remember: Do NOT proceed to step-05 until user explicitly selects 'C' from the A/P/C menu and content is saved!
|
|
@@ -197,7 +197,7 @@ Show the generated inspiration analysis content and present choices:
|
|
|
197
197
|
|
|
198
198
|
- Append the final content to `{planning_artifacts}/ux-design-specification.md`
|
|
199
199
|
- Update frontmatter: append step to end of stepsCompleted array
|
|
200
|
-
- Read fully and follow:
|
|
200
|
+
- Read fully and follow: `./step-06-design-system.md`
|
|
201
201
|
|
|
202
202
|
## APPEND TO DOCUMENT:
|
|
203
203
|
|
|
@@ -229,6 +229,6 @@ When user selects 'C', append the content directly to the document using the str
|
|
|
229
229
|
|
|
230
230
|
## NEXT STEP:
|
|
231
231
|
|
|
232
|
-
After user selects 'C' and content is saved to document, load
|
|
232
|
+
After user selects 'C' and content is saved to document, load `./step-06-design-system.md` to choose the appropriate design system approach.
|
|
233
233
|
|
|
234
234
|
Remember: Do NOT proceed to step-06 until user explicitly selects 'C' from the A/P/C menu and content is saved!
|
|
@@ -215,7 +215,7 @@ Show the generated design system content and present choices:
|
|
|
215
215
|
|
|
216
216
|
- Append the final content to `{planning_artifacts}/ux-design-specification.md`
|
|
217
217
|
- Update frontmatter: append step to end of stepsCompleted array
|
|
218
|
-
- Load
|
|
218
|
+
- Load `./step-07-defining-experience.md`
|
|
219
219
|
|
|
220
220
|
## APPEND TO DOCUMENT:
|
|
221
221
|
|
|
@@ -247,6 +247,6 @@ When user selects 'C', append the content directly to the document using the str
|
|
|
247
247
|
|
|
248
248
|
## NEXT STEP:
|
|
249
249
|
|
|
250
|
-
After user selects 'C' and content is saved to document, load
|
|
250
|
+
After user selects 'C' and content is saved to document, load `./step-07-defining-experience.md` to define the core user interaction.
|
|
251
251
|
|
|
252
252
|
Remember: Do NOT proceed to step-07 until user explicitly selects 'C' from the A/P/C menu and content is saved!
|
|
@@ -217,7 +217,7 @@ Show the generated defining experience content and present choices:
|
|
|
217
217
|
|
|
218
218
|
- Append the final content to `{planning_artifacts}/ux-design-specification.md`
|
|
219
219
|
- Update frontmatter: append step to end of stepsCompleted array
|
|
220
|
-
- Load
|
|
220
|
+
- Load `./step-08-visual-foundation.md`
|
|
221
221
|
|
|
222
222
|
## APPEND TO DOCUMENT:
|
|
223
223
|
|
|
@@ -249,6 +249,6 @@ When user selects 'C', append the content directly to the document using the str
|
|
|
249
249
|
|
|
250
250
|
## NEXT STEP:
|
|
251
251
|
|
|
252
|
-
After user selects 'C' and content is saved to document, load
|
|
252
|
+
After user selects 'C' and content is saved to document, load `./step-08-visual-foundation.md` to establish visual design foundation.
|
|
253
253
|
|
|
254
254
|
Remember: Do NOT proceed to step-08 until user explicitly selects 'C' from the A/P/C menu and content is saved!
|
|
@@ -187,7 +187,7 @@ Show the generated visual foundation content and present choices:
|
|
|
187
187
|
|
|
188
188
|
- Append the final content to `{planning_artifacts}/ux-design-specification.md`
|
|
189
189
|
- Update frontmatter: append step to end of stepsCompleted array
|
|
190
|
-
- Load
|
|
190
|
+
- Load `./step-09-design-directions.md`
|
|
191
191
|
|
|
192
192
|
## APPEND TO DOCUMENT:
|
|
193
193
|
|
|
@@ -219,6 +219,6 @@ When user selects 'C', append the content directly to the document using the str
|
|
|
219
219
|
|
|
220
220
|
## NEXT STEP:
|
|
221
221
|
|
|
222
|
-
After user selects 'C' and content is saved to document, load
|
|
222
|
+
After user selects 'C' and content is saved to document, load `./step-09-design-directions.md` to generate design direction mockups.
|
|
223
223
|
|
|
224
224
|
Remember: Do NOT proceed to step-09 until user explicitly selects 'C' from the A/P/C menu and content is saved!
|
|
@@ -187,7 +187,7 @@ Show the generated design direction content and present choices:
|
|
|
187
187
|
|
|
188
188
|
- Append the final content to `{planning_artifacts}/ux-design-specification.md`
|
|
189
189
|
- Update frontmatter: append step to end of stepsCompleted array
|
|
190
|
-
- Load
|
|
190
|
+
- Load `./step-10-user-journeys.md`
|
|
191
191
|
|
|
192
192
|
## APPEND TO DOCUMENT:
|
|
193
193
|
|
|
@@ -219,6 +219,6 @@ When user selects 'C', append the content directly to the document using the str
|
|
|
219
219
|
|
|
220
220
|
## NEXT STEP:
|
|
221
221
|
|
|
222
|
-
After user selects 'C' and content is saved to document, load
|
|
222
|
+
After user selects 'C' and content is saved to document, load `./step-10-user-journeys.md` to design user journey flows.
|
|
223
223
|
|
|
224
224
|
Remember: Do NOT proceed to step-10 until user explicitly selects 'C' from the A/P/C menu and content is saved!
|