@hanzlaa/rcode 3.6.16 → 4.1.0

package/rcode/skills/actions/1-analysis/research/rcode-domain-research/workflow.md

@@ -0,0 +1,49 @@
+# Domain Research Workflow
+
+**Goal:** Conduct comprehensive domain/industry research using current web data and verified sources to produce complete research documents with compelling narratives and proper citations.
+
+**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.
+
+## PREREQUISITE
+
+**⛔ Web search required.** If unavailable, abort and tell the user.
+
+## CONFIGURATION
+
+Load config from `{project-root}/.rcode/config.json` and resolve:
+- `project_name`, `output_folder`, `planning_artifacts`, `user_name`
+- `communication_language`, `document_output_language`, `user_skill_level`
+- `date` as a system-generated value
+
+## QUICK TOPIC DISCOVERY
+
+"Welcome {{user_name}}! Let's get started with your **domain/industry research**.
+
+**What domain, industry, or sector do you want to research?**
+
+For example:
+- 'The healthcare technology industry'
+- 'Sustainable packaging regulations in Europe'
+- 'Construction and building materials sector'
+- 'Or any other domain you have in mind...'"
+
+### Topic Clarification
+
+Based on the user's topic, briefly clarify:
+1. **Core Domain**: "What specific aspect of [domain] are you most interested in?"
+2. **Research Goals**: "What do you hope to achieve with this research?"
+3. **Scope**: "Should we focus broadly or dive deep into specific aspects?"
+
+## ROUTE TO DOMAIN RESEARCH STEPS
+
+After gathering the topic and goals:
+
+1. Set `research_type = "domain"`
+2. Set `research_topic = [discovered topic from discussion]`
+3. Set `research_goals = [discovered goals from discussion]`
+4. Create the starter output file: `{planning_artifacts}/research/domain-{{research_topic}}-research-{{date}}.md` with exact copy of the `./research.template.md` contents
+5. Load: `./domain-steps/step-01-init.md` with topic context
+
+**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.
+
+**✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`**

package/rcode/skills/actions/1-analysis/research/rcode-market-research/SKILL.md

@@ -0,0 +1,45 @@
+---
+name: rcode-market-research
+internal: true
+description: >
+  Analyze market size, competitive landscape, customer needs, and trends for
+  a product or industry. Activates when the user says "market research",
+  "competitive analysis", "market analysis for", "size the market",
+  "competitor scan", or "analyze the market for X". Do NOT use for domain
+  deep-dives (use rcode-domain-research) or technical feasibility.
+triggers:
+  - "market research"
+  - "competitive analysis"
+  - "market analysis for"
+  - "size the market"
+  - "competitor scan"
+  - "analyze the market for X"
+user-invocable: true
+---
+@.rcode/references/karpathy-guidelines.md
+
+
+## Overview
+
+Analyze market size, competitive landscape, customer needs, and trends for a product or industry.
+
+## Workflow
+
+Follow the instructions in ./workflow.md.
+
+## Output Format
+
+- Report: TAM/SAM/SOM (with sources) | Direct Competitors (3-5) | Indirect Alternatives | Customer Segments | Trends | Recommendation
+- Every number cites a source
+- Saved to .rcode/artifacts/research/market-{slug}.md
+- Do NOT invent market sizes
+
+## Examples
+
+### Happy Path
+**Input:** "Market research for AI legal assistants in the GCC"
+**Expected behavior:** Source-backed TAM/SAM/SOM, competitor scan, segment analysis, recommendation.
+
+### Edge Case: Niche Market
+**Input:** (tiny addressable market)
+**Expected behavior:** Report honestly: "SAM is ~$X — may be too small for VC-scale investment. Consider adjacency or pivot."

package/rcode/skills/actions/1-analysis/research/rcode-market-research/workflow.md

@@ -0,0 +1,49 @@
+# Market Research Workflow
+
+**Goal:** Conduct comprehensive market research using current web data and verified sources to produce complete research documents with compelling narratives and proper citations.
+
+**Your Role:** You are a market 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.
+
+## PREREQUISITE
+
+**⛔ Web search required.** If unavailable, abort and tell the user.
+
+## CONFIGURATION
+
+Load config from `{project-root}/.rcode/config.json` and resolve:
+- `project_name`, `output_folder`, `planning_artifacts`, `user_name`
+- `communication_language`, `document_output_language`, `user_skill_level`
+- `date` as a system-generated value
+
+## QUICK TOPIC DISCOVERY
+
+"Welcome {{user_name}}! Let's get started with your **market research**.
+
+**What topic, problem, or area do you want to research?**
+
+For example:
+- 'The electric vehicle market in Europe'
+- 'Plant-based food alternatives market'
+- 'Mobile payment solutions in Southeast Asia'
+- 'Or anything else you have in mind...'"
+
+### Topic Clarification
+
+Based on the user's topic, briefly clarify:
+1. **Core Topic**: "What exactly about [topic] are you most interested in?"
+2. **Research Goals**: "What do you hope to achieve with this research?"
+3. **Scope**: "Should we focus broadly or dive deep into specific aspects?"
+
+## ROUTE TO MARKET RESEARCH STEPS
+
+After gathering the topic and goals:
+
+1. Set `research_type = "market"`
+2. Set `research_topic = [discovered topic from discussion]`
+3. Set `research_goals = [discovered goals from discussion]`
+4. Create the starter output file: `{planning_artifacts}/research/market-{{research_topic}}-research-{{date}}.md` with exact copy of the `./research.template.md` contents
+5. Load: `./steps/step-01-init.md` with topic context
+
+**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 market research.
+
+**✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`**

package/rcode/skills/actions/1-analysis/research/rcode-technical-research/SKILL.md

@@ -0,0 +1,48 @@
+---
+name: rcode-technical-research
+internal: true
+description: >
+  Research technical feasibility, architecture options, and implementation
+  approaches for a proposed product or feature. Activates when the user says
+  "technical research", "feasibility study", "research implementation
+  options", "how would we build X", "what stack for", or "technical
+  feasibility for". Do NOT use for final architecture decisions (use
+  rcode-create-architecture) or market analysis.
+triggers:
+  - "technical research"
+  - "feasibility study"
+  - "research implementation
+  options"
+  - "how would we build X"
+  - "what stack for"
+  - "technical
+  feasibility for"
+user-invocable: true
+---
+@.rcode/references/karpathy-guidelines.md
+
+
+## Overview
+
+Research technical feasibility, architecture options, and implementation approaches for a proposed product or feature.
+
+## Workflow
+
+Follow the instructions in ./workflow.md.
+
+## Output Format
+
+- Report: Problem Framing | Approach Options (3+) | Trade-off Table | Recommended Approach | Risks | Next Steps
+- Each approach is feasible and buildable with known tech
+- Do NOT propose speculative tech without disclaimer
+- Saved to .rcode/artifacts/research/technical-{slug}.md
+
+## Examples
+
+### Happy Path
+**Input:** "Technical research: how to build real-time collaboration like Figma"
+**Expected behavior:** Compare CRDTs vs OT vs event sourcing, trade-off table, recommended approach with risks.
+
+### Edge Case: Speculative Request
+**Input:** "Research how to build AGI"
+**Expected behavior:** Decline speculative. "This is a research problem, not a technical feasibility. I can research narrower applications of current AI tech instead."

package/rcode/skills/actions/1-analysis/research/rcode-technical-research/workflow.md

@@ -0,0 +1,50 @@
+
+# Technical Research Workflow
+
+**Goal:** Conduct comprehensive technical research using current web data and verified sources to produce complete research documents with compelling narratives and proper citations.
+
+**Your Role:** You are a technical 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.
+
+## PREREQUISITE
+
+**⛔ Web search required.** If unavailable, abort and tell the user.
+
+## CONFIGURATION
+
+Load config from `{project-root}/.rcode/config.json` and resolve:
+- `project_name`, `output_folder`, `planning_artifacts`, `user_name`
+- `communication_language`, `document_output_language`, `user_skill_level`
+- `date` as a system-generated value
+
+## QUICK TOPIC DISCOVERY
+
+"Welcome {{user_name}}! Let's get started with your **technical research**.
+
+**What technology, tool, or technical area do you want to research?**
+
+For example:
+- 'React vs Vue for large-scale applications'
+- 'GraphQL vs REST API architectures'
+- 'Serverless deployment options for Node.js'
+- 'Or any other technical topic you have in mind...'"
+
+### Topic Clarification
+
+Based on the user's topic, briefly clarify:
+1. **Core Technology**: "What specific aspect of [technology] are you most interested in?"
+2. **Research Goals**: "What do you hope to achieve with this research?"
+3. **Scope**: "Should we focus broadly or dive deep into specific aspects?"
+
+## ROUTE TO TECHNICAL RESEARCH STEPS
+
+After gathering the topic and goals:
+
+1. Set `research_type = "technical"`
+2. Set `research_topic = [discovered topic from discussion]`
+3. Set `research_goals = [discovered goals from discussion]`
+4. Create the starter output file: `{planning_artifacts}/research/technical-{{research_topic}}-research-{{date}}.md` with exact copy of the `./research.template.md` contents
+5. Load: `./technical-steps/step-01-init.md` with topic context
+
+**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 technical research.
+
+**✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`**

package/rcode/skills/actions/2-plan/rcode-create-epics-and-stories/SKILL.md

@@ -0,0 +1,58 @@
+---
+name: rcode-create-epics-and-stories
+internal: true
+description: >
+  Break a PRD into epics and user stories that drive development. Activates
+  when the user says "create epics", "break this into stories", "generate
+  the epic list", "epic and story breakdown", "decompose the PRD", or
+  "create the backlog". Do NOT use to prepare a single story for dev (use
+  rcode-create-story).
+triggers:
+  # English
+  - "create epics"
+  - "break this into stories"
+  - "generate the epic list"
+  - "epic and story breakdown"
+  - "decompose the PRD"
+  - "create the backlog"
+  # Roman Urdu / Hindi
+  - "epics banao"
+  - "stories banao"
+  - "backlog banao"
+  # Arabic native
+  - "أنشئ ملاحم"
+  - "أنشئ القصص"
+  - "قسّم المتطلبات"
+  - "ابني القائمة"
+  - "تحليل وثيقة المتطلبات"
+user-invocable: true
+---
+@.rcode/references/karpathy-guidelines.md
+
+
+## Overview
+
+Break a PRD into epics and user stories that drive development.
+
+## Workflow
+
+Follow the instructions in ./workflow.md.
+
+## Output Format
+
+- Produces .rcode/phases/{phase}/epics.md with hierarchical structure
+- Each epic has: Title | Goal | Assumptions | Stories (list) | Priority | Estimate
+- Each story is independently testable and under 4-hour estimate
+- Do NOT create epics larger than 10 stories — split further
+- Every epic must include an `Assumptions` line — at minimum one entry; "none" is not acceptable
+- Every story must have a one-line verifiable AC before being listed — vague stories get flagged and blocked
+
+## Examples
+
+### Happy Path
+**Input:** "Break the PRD into epics and stories"
+**Expected behavior:** Read PRD, identify 3-6 epics aligned with requirements, decompose each into 3-8 stories with clear acceptance criteria. Save to epics.md.
+
+### Edge Case: PRD Missing
+**Input:** "Create epics" (no PRD exists)
+**Expected behavior:** Refuse. Respond: "No PRD found. Run rcode-create-prd first. I cannot invent requirements."

package/rcode/skills/actions/2-plan/rcode-create-epics-and-stories/steps/step-02-design-epics.md

@@ -0,0 +1,212 @@
+# Step 2: Design Epic List
+
+## STEP GOAL:
+
+To design and get approval for the epics_list that will organize all requirements into user-value-focused epics.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are a product strategist and technical specifications writer
+- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring product strategy and epic design expertise
+- ✅ User brings their product vision and priorities
+
+### Step-Specific Rules:
+
+- 🎯 Focus ONLY on creating the epics_list
+- 🚫 FORBIDDEN to create individual stories in this step
+- 💬 Organize epics around user value, not technical layers
+- 🚪 GET explicit approval for the epics_list
+- 🔗 **CRITICAL: Each epic must be standalone and enable future epics without requiring future epics to function**
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Design epics collaboratively based on extracted requirements
+- 💾 Update {{epics_list}} in {planning_artifacts}/epics.md
+- 📖 Document the FR coverage mapping
+- 🚫 FORBIDDEN to load next step until user approves epics_list
+
+## EPIC DESIGN PROCESS:
+
+### 1. Review Extracted Requirements
+
+Load {planning_artifacts}/epics.md and review:
+
+- **Functional Requirements:** Count and review FRs from Step 1
+- **Non-Functional Requirements:** Review NFRs that need to be addressed
+- **Additional Requirements:** Review technical and UX requirements
+
+### 2. Explain Epic Design Principles
+
+**EPIC DESIGN PRINCIPLES:**
+
+1. **User-Value First**: Each epic must enable users to accomplish something meaningful
+2. **Requirements Grouping**: Group related FRs that deliver cohesive user outcomes
+3. **Incremental Delivery**: Each epic should deliver value independently
+4. **Logical Flow**: Natural progression from user's perspective
+5. **🔗 Dependency-Free Within Epic**: Stories within an epic must NOT depend on future stories
+
+**⚠️ CRITICAL PRINCIPLE:**
+Organize by USER VALUE, not technical layers:
+
+**✅ CORRECT Epic Examples (Standalone & Enable Future Epics):**
+
+- Epic 1: User Authentication & Profiles (users can register, login, manage profiles) - **Standalone: Complete auth system**
+- Epic 2: Content Creation (users can create, edit, publish content) - **Standalone: Uses auth, creates content**
+- Epic 3: Social Interaction (users can follow, comment, like content) - **Standalone: Uses auth + content**
+- Epic 4: Search & Discovery (users can find content and other users) - **Standalone: Uses all previous**
+
+**❌ WRONG Epic Examples (Technical Layers or Dependencies):**
+
+- Epic 1: Database Setup (creates all tables upfront) - **No user value**
+- Epic 2: API Development (builds all endpoints) - **No user value**
+- Epic 3: Frontend Components (creates reusable components) - **No user value**
+- Epic 4: Deployment Pipeline (CI/CD setup) - **No user value**
+
+**🔗 DEPENDENCY RULES:**
+
+- Each epic must deliver COMPLETE functionality for its domain
+- Epic 2 must not require Epic 3 to function
+- Epic 3 can build upon Epic 1 & 2 but must stand alone
+
+### 3. Design Epic Structure Collaboratively
+
+**Step A: Identify User Value Themes**
+
+- Look for natural groupings in the FRs
+- Identify user journeys or workflows
+- Consider user types and their goals
+
+**Step B: Propose Epic Structure**
+For each proposed epic:
+
+1. **Epic Title**: User-centric, value-focused
+2. **User Outcome**: What users can accomplish after this epic
+3. **FR Coverage**: Which FR numbers this epic addresses
+4. **Implementation Notes**: Any technical or UX considerations
+
+**Step C: Create the epics_list**
+
+Format the epics_list as:
+
+```
+## Epic List
+
+### Epic 1: [Epic Title]
+[Epic goal statement - what users can accomplish]
+**FRs covered:** FR1, FR2, FR3, etc.
+
+### Epic 2: [Epic Title]
+[Epic goal statement - what users can accomplish]
+**FRs covered:** FR4, FR5, FR6, etc.
+
+[Continue for all epics]
+```
+
+### 4. Present Epic List for Review
+
+Display the complete epics_list to user with:
+
+- Total number of epics
+- FR coverage per epic
+- User value delivered by each epic
+- Any natural dependencies
+
+### 5. Create Requirements Coverage Map
+
+Create {{requirements_coverage_map}} showing how each FR maps to an epic:
+
+```
+### FR Coverage Map
+
+FR1: Epic 1 - [Brief description]
+FR2: Epic 1 - [Brief description]
+FR3: Epic 2 - [Brief description]
+...
+```
+
+This ensures no FRs are missed.
+
+### 6. Collaborative Refinement
+
+Ask user:
+
+- "Does this epic structure align with your product vision?"
+- "Are all user outcomes properly captured?"
+- "Should we adjust any epic groupings?"
+- "Are there natural dependencies we've missed?"
+
+### 7. Get Final Approval
+
+**CRITICAL:** Must get explicit user approval:
+"Do you approve this epic structure for proceeding to story creation?"
+
+If user wants changes:
+
+- Make the requested adjustments
+- Update the epics_list
+- Re-present for approval
+- Repeat until approval is received
+
+## CONTENT TO UPDATE IN DOCUMENT:
+
+After approval, update {planning_artifacts}/epics.md:
+
+1. Replace {{epics_list}} placeholder with the approved epic list
+2. Replace {{requirements_coverage_map}} with the coverage map
+3. Ensure all FRs are mapped to epics
+
+### 8. Present MENU OPTIONS
+
+Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
+
+#### Menu Handling Logic:
+
+- IF A: Invoke the `rcode-advanced-elicitation` skill
+- IF P: Invoke the `rcode-party-mode` skill
+- IF C: Save approved epics_list to {planning_artifacts}/epics.md, update frontmatter, then read fully and follow: ./step-03-create-stories.md
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#8-present-menu-options)
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- After other menu items execution completes, redisplay the menu
+- User can chat or ask questions - always respond when conversation ends, redisplay the menu options
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN C is selected and the approved epics_list is saved to document, will you then read fully and follow: ./step-03-create-stories.md to begin story creation step.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Epics designed around user value
+- All FRs mapped to specific epics
+- epics_list created and formatted correctly
+- Requirements coverage map completed
+- User gives explicit approval for epic structure
+- Document updated with approved epics
+
+### ❌ SYSTEM FAILURE:
+
+- Epics organized by technical layers
+- Missing FRs in coverage map
+- No user approval obtained
+- epics_list not saved to document
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.