wize-dev-kit 0.3.0 → 0.4.0

package/src/method-skills/1-analysis/wize-domain-research/domain-steps/step-06-research-synthesis.md

@@ -0,0 +1,43 @@
+# Step 6: Domain Research Synthesis and Completion
+
+## Rules
+
+- 🌐 Search the web to verify claims.
+- 📝 Replace the Research Overview placeholder and append synthesis.
+- ✅ Speak in `{communication_language}`; write artifacts in `{document_output_language}`.
+
+## Task
+
+Produce the final domain research synthesis.
+
+## Execution
+
+Replace `[Research overview and methodology will be appended here.]` with a concise summary.
+
+Append:
+
+```markdown
+## Research Synthesis
+
+### Key Findings
+1. ...
+2. ...
+
+### Strategic Implications
+...
+
+### Constraints for the Product
+...
+
+### Still Open
+- ...
+
+### Sources
+...
+```
+
+Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6]` and `status: complete`.
+
+## On complete
+
+Run `{workflow.on_complete}` if non-empty.

package/src/method-skills/1-analysis/wize-domain-research/research.template.md

@@ -0,0 +1,31 @@
+---
+research_type: domain
+research_topic: "{{research_topic}}"
+research_goals: "{{research_goals}}"
+status: in-progress
+stepsCompleted: []
+owner: Pepper Potts
+created: "{{date}}"
+---
+
+# Domain Research — {{research_topic}}
+
+## Research Overview
+
+[Research overview and methodology will be appended here.]
+
+## Scope Confirmation
+
+## Domain Analysis
+
+## Competitive Landscape
+
+## Regulatory Focus
+
+## Technical Trends
+
+## Research Synthesis
+
+## Sources
+
+## Open Questions

package/src/method-skills/1-analysis/wize-domain-research/workflow.md

@@ -0,0 +1,51 @@
+---
+code: wize-domain-research
+name: Domain Research
+phase: 1-analysis
+owner: wize-agent-analyst   # Pepper Potts
+status: ready
+---
+
+# Domain Research
+
+**Goal.** Conduct domain and industry research to ground the product in its business, regulatory, and technical context.
+
+Pepper Potts drives. Peggy Carter edits prose. Output lands in `.wize/planning/research/domain-{slug}-research-{date}.md`.
+
+## When to use
+
+- "I need domain research on..."
+- "What are the regulations in this industry?"
+- "What are the technical trends in this sector?"
+
+## Inputs
+
+- Open questions from `.wize/planning/brief.md`
+- User-provided domain or industry
+- Web search access
+
+## Outputs
+
+- `.wize/planning/research/domain-{slug}-research-{date}.md`
+
+## Workflow architecture
+
+Step-file architecture with six steps:
+
+1. Scope confirmation
+2. Domain analysis
+3. Competitive landscape
+4. Regulatory focus
+5. Technical trends
+6. Research synthesis
+
+## On activation
+
+1. Load `.wize/config/project.toml` and `.wize/config/user.toml`.
+2. Ask for the domain/industry topic if not provided.
+3. Derive `{research_topic_slug}` and create the output file from `research.template.md`.
+4. Read fully and follow `./domain-steps/step-01-init.md`.
+
+## Hand-off
+
+> Domain research is in `.wize/planning/research/`. Hill can use it for PRD constraints; open questions route back to Wizer.

package/src/method-skills/1-analysis/wize-market-research/customize.toml

@@ -0,0 +1,14 @@
+# Wize Dev Kit — overrides for the built-in workflow "wize-market-research".
+# DO NOT EDIT in the installed kit; copy to .wize/custom/workflows/wize-market-research/
+# for project-level overrides.
+
+[workflow]
+
+activation_steps_prepend = []
+activation_steps_append = []
+
+persistent_facts = [
+  "file:{project-root}/.wize/planning/brief.md",
+]
+
+on_complete = ""

package/src/method-skills/1-analysis/wize-market-research/research.template.md

@@ -0,0 +1,31 @@
+---
+research_type: market
+research_topic: "{{research_topic}}"
+research_goals: "{{research_goals}}"
+status: in-progress
+stepsCompleted: []
+owner: Pepper Potts
+created: "{{date}}"
+---
+
+# Market Research — {{research_topic}}
+
+## Research Overview
+
+[Research overview and methodology will be appended here.]
+
+## Scope Confirmation
+
+## Customer Behavior Analysis
+
+## Customer Pain Points
+
+## Customer Decisions
+
+## Competitive Analysis
+
+## Research Synthesis
+
+## Sources
+
+## Open Questions

package/src/method-skills/1-analysis/wize-market-research/steps/step-01-init.md

@@ -0,0 +1,57 @@
+# Step 1: Market Research Scope Confirmation
+
+## Rules
+
+- 🛑 Never generate content without user confirmation.
+- 📖 Always read the complete step file before acting.
+- 🔍 This is scope confirmation only — no web research yet.
+- ✅ Speak in `{communication_language}`; write artifacts in `{document_output_language}`.
+
+## Context
+
+- Research type = "market"
+- Research topic = "{{research_topic}}"
+- Research goals = "{{research_goals}}"
+
+## Task
+
+Confirm market research scope and approach.
+
+## Execution
+
+Present the scope:
+
+```
+I understand you want market research for {{research_topic}}.
+
+This research will cover:
+✅ Customer behavior
+✅ Customer pain points
+✅ Customer decisions and jobs-to-be-done
+✅ Competitive landscape
+✅ Market positioning implications
+
+All claims will be verified against current public sources.
+
+[C] Continue — begin market research with this scope
+```
+
+When the user selects [C], append the scope confirmation to the document and update frontmatter `stepsCompleted: [1]`, then load `./step-02-customer-behavior.md`.
+
+## Append to document
+
+```markdown
+## Market Research Scope Confirmation
+
+**Research Topic:** {{research_topic}}
+**Research Goals:** {{research_goals}}
+
+**Scope:**
+- Customer behavior
+- Customer pain points
+- Customer decisions and jobs-to-be-done
+- Competitive landscape
+- Market positioning implications
+
+**Scope Confirmed:** {{date}}
+```

package/src/method-skills/1-analysis/wize-market-research/steps/step-02-customer-behavior.md

@@ -0,0 +1,39 @@
+# Step 2: Customer Behavior Analysis
+
+## Rules
+
+- 🌐 Search the web to verify claims.
+- 📝 Write findings to the document immediately.
+- ✅ Speak in `{communication_language}`; write artifacts in `{document_output_language}`.
+
+## Task
+
+Analyze customer behavior for {{research_topic}}.
+
+## Execution
+
+Run parallel web searches:
+
+- "{{research_topic}} customer behavior trends"
+- "{{research_topic}} user demographics"
+- "{{research_topic}} usage patterns"
+
+Synthesize and append:
+
+```markdown
+## Customer Behavior Analysis
+
+### Target Audience
+...
+
+### Usage Patterns
+...
+
+### Trends
+...
+
+### Source Citations
+...
+```
+
+Update frontmatter `stepsCompleted: [1, 2]`, then load `./step-03-customer-pain-points.md`.

package/src/method-skills/1-analysis/wize-market-research/steps/step-03-customer-pain-points.md

@@ -0,0 +1,37 @@
+# Step 3: Customer Pain Points
+
+## Rules
+
+- 🌐 Search the web to verify claims.
+- 📝 Write findings to the document immediately.
+- ✅ Speak in `{communication_language}`; write artifacts in `{document_output_language}`.
+
+## Task
+
+Identify customer pain points for {{research_topic}}.
+
+## Execution
+
+Search for:
+
+- "{{research_topic}} customer complaints"
+- "{{research_topic}} common frustrations"
+- "{{research_topic}} Reddit / G2 / Capterra reviews"
+
+Synthesize and append:
+
+```markdown
+## Customer Pain Points
+
+### Top Pain Points
+1. ...
+2. ...
+
+### Evidence
+...
+
+### Source Citations
+...
+```
+
+Update frontmatter `stepsCompleted: [1, 2, 3]`, then load `./step-04-customer-decisions.md`.

package/src/method-skills/1-analysis/wize-market-research/steps/step-04-customer-decisions.md

@@ -0,0 +1,39 @@
+# Step 4: Customer Decisions
+
+## Rules
+
+- 🌐 Search the web to verify claims.
+- 📝 Write findings to the document immediately.
+- ✅ Speak in `{communication_language}`; write artifacts in `{document_output_language}`.
+
+## Task
+
+Map the customer decision journey for {{research_topic}}.
+
+## Execution
+
+Search for:
+
+- "{{research_topic}} buyer journey"
+- "{{research_topic}} purchase criteria"
+- "{{research_topic}} jobs to be done"
+
+Synthesize and append:
+
+```markdown
+## Customer Decisions
+
+### Jobs-to-be-Done
+...
+
+### Decision Criteria
+...
+
+### Switching Triggers
+...
+
+### Source Citations
+...
+```
+
+Update frontmatter `stepsCompleted: [1, 2, 3, 4]`, then load `./step-05-competitive-analysis.md`.

package/src/method-skills/1-analysis/wize-market-research/steps/step-05-competitive-analysis.md

@@ -0,0 +1,37 @@
+# Step 5: Competitive Analysis
+
+## Rules
+
+- 🌐 Search the web to verify claims.
+- 📝 Write findings to the document immediately.
+- ✅ Speak in `{communication_language}`; write artifacts in `{document_output_language}`.
+
+## Task
+
+Analyze competitors for {{research_topic}}.
+
+## Execution
+
+Search for:
+
+- "{{research_topic}} competitors"
+- "{{research_topic}} alternative solutions"
+- "{{research_topic}} pricing comparison"
+
+Synthesize and append:
+
+```markdown
+## Competitive Analysis
+
+### Competitor Matrix
+| Competitor | Positioning | Pricing | Strengths | Weaknesses |
+|---|---|---|---|---|
+
+### Differentiation Opportunities
+...
+
+### Source Citations
+...
+```
+
+Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5]`, then load `./step-06-research-completion.md`.

package/src/method-skills/1-analysis/wize-market-research/steps/step-06-research-completion.md

@@ -0,0 +1,47 @@
+# Step 6: Market Research Synthesis and Completion
+
+## Rules
+
+- 🌐 Search the web to verify claims.
+- ✅ Speak in `{communication_language}`; write artifacts in `{document_output_language}`.
+- 📝 Replace the placeholder in the Research Overview section with a concise summary.
+
+## Task
+
+Produce the final market research synthesis.
+
+## Execution
+
+Replace `[Research overview and methodology will be appended here.]` with:
+
+```markdown
+This report covers customer behavior, pain points, decision drivers, and competitive dynamics for {{research_topic}}. The synthesis highlights the most important findings and their implications for the product brief and PRD.
+```
+
+Append:
+
+```markdown
+## Research Synthesis
+
+### Key Findings
+1. ...
+2. ...
+
+### Implications for Product Brief
+...
+
+### Implications for PRD
+...
+
+### Still Open
+- ...
+
+### Sources
+...
+```
+
+Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5, 6]` and `status: complete`.
+
+## On complete
+
+Run `{workflow.on_complete}` if non-empty.

package/src/method-skills/1-analysis/wize-market-research/workflow.md

@@ -0,0 +1,59 @@
+---
+code: wize-market-research
+name: Market Research
+phase: 1-analysis
+owner: wize-agent-analyst   # Pepper Potts
+status: ready
+---
+
+# Market Research
+
+**Goal.** Conduct market research on competition and customers to inform the product brief and PRD.
+
+Pepper Potts drives. Peggy Carter edits prose. Output lands in `.wize/planning/research/market-{slug}-research-{date}.md`.
+
+## When to use
+
+- "I need market research on..."
+- "Who are the competitors?"
+- "What do customers actually want?"
+
+## Inputs
+
+- Open questions from `.wize/planning/brief.md`
+- User-provided topic or problem area
+- Web search access
+
+## Outputs
+
+- `.wize/planning/research/market-{slug}-research-{date}.md`
+
+## Workflow architecture
+
+This skill uses **step-file architecture**:
+
+- Six steps, each self-contained.
+- Sequential progression with user control.
+- Document state tracked in frontmatter (`stepsCompleted`).
+
+## On activation
+
+1. Load `.wize/config/project.toml` and `.wize/config/user.toml`.
+2. Resolve language settings and output paths.
+3. Greet the user in `communication_language`.
+4. Ask for the market research topic if not provided.
+5. Derive `{research_topic_slug}` and create the output file from `research.template.md`.
+6. Read fully and follow `./steps/step-01-init.md`.
+
+## Steps
+
+1. `step-01-init.md` — confirm scope.
+2. `step-02-customer-behavior.md` — analyze customer behavior.
+3. `step-03-customer-pain-points.md` — identify pain points.
+4. `step-04-customer-decisions.md` — map purchase/journey decisions.
+5. `step-05-competitive-analysis.md` — analyze competitors.
+6. `step-06-research-completion.md` — synthesize and complete.
+
+## Hand-off
+
+> Market research document is in `.wize/planning/research/`. Hill can quote the findings in the PRD; open questions route back to Wizer.

package/src/method-skills/1-analysis/wize-technical-research/customize.toml

@@ -0,0 +1,14 @@
+# Wize Dev Kit — overrides for the built-in workflow "wize-technical-research".
+# DO NOT EDIT in the installed kit; copy to .wize/custom/workflows/wize-technical-research/
+# for project-level overrides.
+
+[workflow]
+
+activation_steps_prepend = []
+activation_steps_append = []
+
+persistent_facts = [
+  "file:{project-root}/.wize/planning/brief.md",
+]
+
+on_complete = ""

package/src/method-skills/1-analysis/wize-technical-research/research.template.md

@@ -0,0 +1,31 @@
+---
+research_type: technical
+research_topic: "{{research_topic}}"
+research_goals: "{{research_goals}}"
+status: in-progress
+stepsCompleted: []
+owner: Pepper Potts
+created: "{{date}}"
+---
+
+# Technical Research — {{research_topic}}
+
+## Research Overview
+
+[Research overview and methodology will be appended here.]
+
+## Scope Confirmation
+
+## Technology Stack Analysis
+
+## Integration Patterns
+
+## Architectural Patterns
+
+## Implementation Research
+
+## Research Synthesis
+
+## Sources
+
+## Open Questions

package/src/method-skills/1-analysis/wize-technical-research/technical-steps/step-01-init.md

@@ -0,0 +1,49 @@
+# Step 1: Technical Research Scope Confirmation
+
+## Rules
+
+- 🛑 Never generate content without user confirmation.
+- 📖 Always read the complete step file before acting.
+- 🔍 Scope confirmation only.
+- ✅ Speak in `{communication_language}`; write artifacts in `{document_output_language}`.
+
+## Task
+
+Confirm technical research scope.
+
+## Execution
+
+Present:
+
+```
+I understand you want technical research for {{research_topic}}.
+
+This research will cover:
+✅ Technology stack and tooling
+✅ Integration patterns
+✅ Architectural patterns
+✅ Implementation approaches
+✅ Performance and scalability considerations
+
+[C] Continue — begin technical research with this scope
+```
+
+On [C], append the scope confirmation, update `stepsCompleted: [1]`, and load `./technical-steps/step-02-technical-overview.md`.
+
+## Append
+
+```markdown
+## Technical Research Scope Confirmation
+
+**Research Topic:** {{research_topic}}
+**Research Goals:** {{research_goals}}
+
+**Scope:**
+- Technology stack and tooling
+- Integration patterns
+- Architectural patterns
+- Implementation approaches
+- Performance and scalability considerations
+
+**Scope Confirmed:** {{date}}
+```

package/src/method-skills/1-analysis/wize-technical-research/technical-steps/step-02-technical-overview.md

@@ -0,0 +1,45 @@
+# Step 2: Technology Stack Analysis
+
+## Rules
+
+- 🌐 Search the web to verify claims.
+- 📝 Write findings to the document immediately.
+- ✅ Speak in `{communication_language}`; write artifacts in `{document_output_language}`.
+
+## Task
+
+Analyze the technology stack landscape for {{research_topic}}.
+
+## Execution
+
+Search for:
+
+- "{{research_topic}} programming languages frameworks"
+- "{{research_topic}} development tools platforms"
+- "{{research_topic}} database storage technologies"
+
+Synthesize and append:
+
+```markdown
+## Technology Stack Analysis
+
+### Programming Languages
+...
+
+### Frameworks and Libraries
+...
+
+### Database and Storage
+...
+
+### Development Tools and Platforms
+...
+
+### Cloud Infrastructure and Deployment
+...
+
+### Source Citations
+...
+```
+
+Update `stepsCompleted: [1, 2]` and load `./technical-steps/step-03-integration-patterns.md`.

package/src/method-skills/1-analysis/wize-technical-research/technical-steps/step-03-integration-patterns.md

@@ -0,0 +1,39 @@
+# Step 3: Integration Patterns
+
+## Rules
+
+- 🌐 Search the web to verify claims.
+- 📝 Write findings to the document immediately.
+- ✅ Speak in `{communication_language}`; write artifacts in `{document_output_language}`.
+
+## Task
+
+Analyze integration patterns for {{research_topic}}.
+
+## Execution
+
+Search for:
+
+- "{{research_topic}} API design patterns"
+- "{{research_topic}} service integration"
+- "{{research_topic}} data integration"
+
+Synthesize and append:
+
+```markdown
+## Integration Patterns
+
+### API Design Patterns
+...
+
+### Service Integration
+...
+
+### Data Integration
+...
+
+### Source Citations
+...
+```
+
+Update `stepsCompleted: [1, 2, 3]` and load `./technical-steps/step-04-architectural-patterns.md`.