@hanzlaa/rcode 3.6.15 → 4.0.0

package/rihal/skills/actions/2-plan/rihal-edit-prd/steps-e/step-e-02-review.md

@@ -1,245 +0,0 @@
----
-# File references (ONLY variables used in this step)
-prdFile: '{prd_file_path}'
-validationReport: '{validation_report_path}'  # If provided
-prdPurpose: '{project-root}/_rihal-skills/2-plan-workflows/create-prd/data/prd-purpose.md'
----
-
-# Step E-2: Deep Review & Analysis
-
-## STEP GOAL:
-
-Thoroughly review the existing PRD, analyze validation report findings (if provided), and prepare a detailed change plan before editing.
-
-## 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}`
-- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
-
-### Role Reinforcement:
-
-- ✅ You are a Validation Architect and PRD Improvement Specialist
-- ✅ 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 analytical expertise and improvement planning
-- ✅ User brings domain knowledge and approval authority
-
-### Step-Specific Rules:
-
-- 🎯 Focus ONLY on review and analysis, not editing yet
-- 🚫 FORBIDDEN to make changes to PRD in this step
-- 💬 Approach: Thorough analysis with user confirmation on plan
-- 🚪 This is a middle step - user confirms plan before proceeding
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load and analyze validation report (if provided)
-- 🎯 Deep review of entire PRD
-- 🎯 Map validation findings to specific sections
-- 🎯 Prepare detailed change plan
-- 💬 Get user confirmation on plan
-- 🚫 FORBIDDEN to proceed to edit without user approval
-
-## CONTEXT BOUNDARIES:
-
-- Available context: PRD file, validation report (if provided), user requirements from step e-01
-- Focus: Analysis and planning only (no editing)
-- Limits: Don't change PRD yet, don't validate yet
-- Dependencies: Step e-01 completed - requirements and format known
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
-
-### 1. Attempt Sub-Process Deep Review
-
-**Try to use Task tool with sub-agent:**
-
-"Perform deep PRD review and change planning:
-
-**Context from step e-01:**
-- User's edit requirements: {user_requirements}
-- PRD format: {Rihal/legacy}
-- Validation report provided: {yes/no}
-- Conversion mode: {restructure/targeted/both} (if legacy)
-
-**IF validation report provided:**
-1. Extract all findings from validation report
-2. Map findings to specific PRD sections
-3. Prioritize by severity: Critical > Warning > Informational
-4. For each critical issue: identify specific fix needed
-5. For user's manual edit goals: identify where in PRD to apply
-
-**IF no validation report:**
-1. Read entire PRD thoroughly
-2. Analyze against Rihal standards (from prd-purpose.md)
-3. Identify issues in:
-   - Information density (anti-patterns)
-   - Structure and flow
-   - Completeness (missing sections/content)
-   - Measurability (unmeasurable requirements)
-   - Traceability (broken chains)
-   - Implementation leakage
-4. Map user's edit goals to specific sections
-
-**Output:**
-- Section-by-section analysis
-- Specific changes needed for each section
-- Prioritized action list
-- Recommended order for applying changes
-
-Return detailed change plan with section breakdown."
-
-**Graceful degradation (if no Task tool):**
-- Manually read PRD sections
-- Manually analyze validation report findings (if provided)
-- Build section-by-section change plan
-- Prioritize changes by severity/user goals
-
-### 2. Build Change Plan
-
-**Organize by PRD section:**
-
-**For each section (in order):**
-- **Current State:** Brief description of what exists
-- **Issues Identified:** [List from validation report or manual analysis]
-- **Changes Needed:** [Specific changes required]
-- **Priority:** [Critical/High/Medium/Low]
-- **User Requirements Met:** [Which user edit goals address this section]
-
-**Include:**
-- Sections to add (if missing)
-- Sections to update (if present but needs work)
-- Content to remove (if incorrect/leakage)
-- Structure changes (if reformatting needed)
-
-### 3. Prepare Change Plan Summary
-
-**Summary sections:**
-
-**Changes by Type:**
-- **Additions:** {count} sections to add
-- **Updates:** {count} sections to update
-- **Removals:** {count} items to remove
-- **Restructuring:** {yes/no} if format conversion needed
-
-**Priority Distribution:**
-- **Critical:** {count} changes (must fix)
-- **High:** {count} changes (important)
-- **Medium:** {count} changes (nice to have)
-- **Low:** {count} changes (optional)
-
-**Estimated Effort:**
-[Quick/Moderate/Substantial] based on scope and complexity
-
-### 4. Present Change Plan to User
-
-Display:
-
-"**Deep Review Complete - Change Plan**
-
-**PRD Analysis:**
-{Brief summary of PRD current state}
-
-{If validation report provided:}
-**Validation Findings:**
-{count} issues identified: {critical} critical, {warning} warnings
-
-**Your Edit Requirements:**
-{summary of what user wants to edit}
-
-**Proposed Change Plan:**
-
-**By Section:**
-{Present section-by-section breakdown}
-
-**By Priority:**
-- Critical: {count} items
-- High: {count} items
-- Medium: {count} items
-
-**Estimated Effort:** {effort level}
-
-**Questions:**
-1. Does this change plan align with what you had in mind?
-2. Any sections I should add/remove/reprioritize?
-3. Any concerns before I proceed with edits?
-
-**Review the plan and let me know if you'd like any adjustments.**"
-
-### 5. Get User Confirmation
-
-Wait for user to review and provide feedback.
-
-**If user wants adjustments:**
-- Discuss requested changes
-- Revise change plan accordingly
-- Represent for confirmation
-
-**If user approves:**
-- Note: "Change plan approved. Proceeding to edit step."
-- Continue to step 6
-
-### 6. Document Approved Plan
-
-Store approved change plan for next step:
-
-- **Approved changes:** Section-by-section list
-- **Priority order:** Sequence to apply changes
-- **User confirmed:** Yes
-
-Display: "**Change Plan Approved**
-
-{Brief summary of approved plan}
-
-**Proceeding to edit step...**"
-
-Read fully and follow: `./step-e-03-edit.md`
-
-### 7. Present MENU OPTIONS (If User Wants Discussion)
-
-**[A] Advanced Elicitation** - Get additional perspectives on change plan
-**[P] Party Mode** - Discuss with team for more ideas
-**[C] Continue to Edit** - Proceed with approved plan
-
-#### EXECUTION RULES:
-
-- ALWAYS halt and wait for user input
-- Only proceed to edit when user selects 'C'
-
-#### Menu Handling Logic:
-
-- IF A: Invoke the `rihal-advanced-elicitation` skill, then return to discussion
-- IF P: Invoke the `rihal-party-mode` skill, then return to discussion
-- IF C: Document approval, then load step-e-03-edit.md
-- IF Any other: discuss, then redisplay menu
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Validation report findings fully analyzed (if provided)
-- Deep PRD review completed systematically
-- Change plan built section-by-section
-- Changes prioritized by severity/user goals
-- User presented with clear plan
-- User confirms or adjusts plan
-- Approved plan documented for next step
-
-### ❌ SYSTEM FAILURE:
-
-- Not analyzing validation report findings (if provided)
-- Superficial review instead of deep analysis
-- Missing section-by-section breakdown
-- Not prioritizing changes
-- Proceeding without user approval
-
-**Master Rule:** Plan before editing. Thorough analysis ensures we make the right changes in the right order. User approval prevents misalignment.

package/rihal/skills/actions/2-plan/rihal-edit-prd/steps-e/step-e-03-edit.md

@@ -1,250 +0,0 @@
----
-# File references (ONLY variables used in this step)
-prdFile: '{prd_file_path}'
-prdPurpose: '{project-root}/_rihal-skills/2-plan-workflows/create-prd/data/prd-purpose.md'
----
-
-# Step E-3: Edit & Update
-
-## STEP GOAL:
-
-Apply changes to the PRD following the approved change plan from step e-02, including content updates, structure improvements, and format conversion if needed.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 ALWAYS generate content WITH user input/approval
-- 📖 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}`
-- ✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`
-
-### Role Reinforcement:
-
-- ✅ You are a Validation Architect and PRD Improvement Specialist
-- ✅ 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 analytical expertise and precise editing skills
-- ✅ User brings domain knowledge and approval authority
-
-### Step-Specific Rules:
-
-- 🎯 Focus ONLY on implementing approved changes from step e-02
-- 🚫 FORBIDDEN to make changes beyond the approved plan
-- 💬 Approach: Methodical, section-by-section execution
-- 🚪 This is a middle step - user can request adjustments
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Follow approved change plan systematically
-- 💾 Edit PRD content according to plan
-- 📖 Update frontmatter as needed
-- 🚫 FORBIDDEN to proceed without completion
-
-## CONTEXT BOUNDARIES:
-
-- Available context: PRD file, approved change plan from step e-02, prd-purpose standards
-- Focus: Implementing changes from approved plan only
-- Limits: Don't add changes beyond plan, don't validate yet
-- Dependencies: Step e-02 completed - plan approved by user
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
-
-### 1. Retrieve Approved Change Plan
-
-From step e-02, retrieve:
-- **Approved changes:** Section-by-section list
-- **Priority order:** Sequence to apply changes
-- **User requirements:** Edit goals from step e-01
-
-Display: "**Starting PRD Edits**
-
-**Change Plan:** {summary}
-**Total Changes:** {count}
-**Estimated Effort:** {effort level}
-
-**Proceeding with edits section by section...**"
-
-### 2. Attempt Sub-Process Edits (For Complex Changes)
-
-**Try to use Task tool with sub-agent for major sections:**
-
-"Execute PRD edits for {section_name}:
-
-**Context:**
-- Section to edit: {section_name}
-- Current content: {existing content}
-- Changes needed: {specific changes from plan}
-- Rihal PRD standards: Load from prd-purpose.md
-
-**Tasks:**
-1. Read current PRD section
-2. Apply specified changes
-3. Ensure Rihal PRD principles compliance:
-   - High information density (no filler)
-   - Measurable requirements
-   - Clear structure
-   - Proper markdown formatting
-4. Return updated section content
-
-Apply changes and return updated section."
-
-**Graceful degradation (if no Task tool):**
-- Perform edits directly in current context
-- Load PRD section, apply changes, save
-
-### 3. Execute Changes Section-by-Section
-
-**For each section in approved plan (in priority order):**
-
-**a) Load current section**
-- Read the current PRD section content
-- Note what exists
-
-**b) Apply changes per plan**
-- Additions: Create new sections with proper content
-- Updates: Modify existing content per plan
-- Removals: Remove specified content
-- Restructuring: Reformat content to Rihal standard
-
-**c) Update PRD file**
-- Apply changes to PRD
-- Save updated PRD
-- Verify changes applied correctly
-
-**Display progress after each section:**
-"**Section Updated:** {section_name}
-Changes: {brief summary}
-{More sections remaining...}"
-
-### 4. Handle Restructuring (If Needed)
-
-**If conversion mode is "Full restructuring" or "Both":**
-
-**For restructuring:**
-- Reorganize PRD to Rihal standard structure
-- Ensure proper ## Level 2 headers
-- Reorder sections logically
-- Update PRD frontmatter to match Rihal format
-
-**Follow Rihal PRD structure:**
-1. Executive Summary
-2. Success Criteria
-3. Product Scope
-4. User Journeys
-5. Domain Requirements (if applicable)
-6. Innovation Analysis (if applicable)
-7. Project-Type Requirements
-8. Functional Requirements
-9. Non-Functional Requirements
-
-Display: "**PRD Restructured**
-Rihal standard structure applied.
-{Sections added/reordered}"
-
-### 5. Update PRD Frontmatter
-
-**Ensure frontmatter is complete and accurate:**
-
-```yaml
----
-workflowType: 'prd'
-workflow: 'create'  # or 'validate' or 'edit'
-classification:
-  domain: '{domain}'
-  projectType: '{project_type}'
-  complexity: '{complexity}'
-inputDocuments: [list of input documents]
-stepsCompleted: ['step-e-01-discovery', 'step-e-02-review', 'step-e-03-edit']
-lastEdited: '{current_date}'
-editHistory:
-  - date: '{current_date}'
-    changes: '{summary of changes}'
----
-```
-
-**Update frontmatter accordingly.**
-
-### 6. Final Review of Changes
-
-**Load complete updated PRD**
-
-**Verify:**
-- All approved changes applied correctly
-- PRD structure is sound
-- No unintended modifications
-- Frontmatter is accurate
-
-**If issues found:**
-- Fix them now
-- Note corrections made
-
-**If user wants adjustments:**
-- Accept feedback and make adjustments
-- Re-verify after adjustments
-
-### 7. Confirm Completion
-
-Display:
-
-"**PRD Edits Complete**
-
-**Changes Applied:** {count} sections modified
-**PRD Updated:** {prd_file_path}
-
-**Summary of Changes:**
-{Brief bullet list of major changes}
-
-**PRD is ready for:**
-- Use in downstream workflows (UX, Architecture)
-- Validation (if not yet validated)
-
-**What would you like to do next?**"
-
-### 8. Present MENU OPTIONS
-
-**[V] Run Validation** - Execute full validation workflow (./steps-v/step-v-01-discovery.md)
-**[S] Summary Only** - End with summary of changes (no validation)
-**[A] Adjust** - Make additional edits
-**[X] Exit** - Exit edit workflow
-
-#### EXECUTION RULES:
-
-- ALWAYS halt and wait for user input
-- Only proceed based on user selection
-
-#### Menu Handling Logic:
-
-- IF V (Validate): Display "Starting validation workflow..." then read fully and follow: `./steps-v/step-v-01-discovery.md`
-- IF S (Summary): Present edit summary and exit
-- IF A (Adjust): Accept additional requirements, loop back to editing
-- IF X (Exit): Display summary and exit
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- All approved changes from step e-02 applied correctly
-- Changes executed in planned priority order
-- Restructuring completed (if needed)
-- Frontmatter updated accurately
-- Final verification confirms changes
-- User can proceed to validation or exit with summary
-- Option to run validation seamlessly integrates edit and validate modes
-
-### ❌ SYSTEM FAILURE:
-
-- Making changes beyond approved plan
-- Not following priority order
-- Missing restructuring (if conversion mode)
-- Not updating frontmatter
-- No final verification
-- Not saving updated PRD
-
-**Master Rule:** Execute the plan exactly as approved. PRD is now ready for validation or downstream use. Validation integration ensures quality.

package/rihal/skills/actions/2-plan/rihal-edit-prd/steps-e/step-e-04-complete.md

@@ -1,165 +0,0 @@
----
-# File references (ONLY variables used in this step)
-prdFile: '{prd_file_path}'
-validationWorkflow: '{project-root}/_rihal-skills/2-plan-workflows/create-prd/steps-v/step-v-01-discovery.md'
----
-
-# Step E-4: Complete & Validate
-
-## STEP GOAL:
-
-Present summary of completed edits and offer next steps including seamless integration with validation workflow.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 ALWAYS generate content WITH user input/approval
-- 📖 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 Validation Architect and PRD Improvement Specialist
-- ✅ 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 synthesis and summary expertise
-- ✅ User chooses next actions
-
-### Step-Specific Rules:
-
-- 🎯 Focus ONLY on presenting summary and options
-- 🚫 FORBIDDEN to make additional changes
-- 💬 Approach: Clear, concise summary with actionable options
-- 🚪 This is the final edit step - no more edits
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Compile summary of all changes made
-- 🎯 Present options clearly with expected outcomes
-- 📖 Route to validation if user chooses
-- 🚫 FORBIDDEN to proceed without user selection
-
-## CONTEXT BOUNDARIES:
-
-- Available context: Updated PRD file, edit history from step e-03
-- Focus: Summary and options only (no more editing)
-- Limits: Don't make changes, just present options
-- Dependencies: Step e-03 completed - all edits applied
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
-
-### 1. Compile Edit Summary
-
-From step e-03 change execution, compile:
-
-**Changes Made:**
-- Sections added: {list with names}
-- Sections updated: {list with names}
-- Content removed: {list}
-- Structure changes: {description}
-
-**Edit Details:**
-- Total sections affected: {count}
-- Mode: {restructure/targeted/both}
-- Priority addressed: {Critical/High/Medium/Low}
-
-**PRD Status:**
-- Format: {Rihal Standard / Rihal Variant / Legacy (converted)}
-- Completeness: {assessment}
-- Ready for: {downstream use cases}
-
-### 2. Present Completion Summary
-
-Display:
-
-"**✓ PRD Edit Complete**
-
-**Updated PRD:** {prd_file_path}
-
-**Changes Summary:**
-{Present bulleted list of major changes}
-
-**Edit Mode:** {mode}
-**Sections Modified:** {count}
-
-**PRD Format:** {format}
-
-**PRD is now ready for:**
-- Downstream workflows (UX Design, Architecture)
-- Validation to ensure quality
-- Production use
-
-**What would you like to do next?**"
-
-### 3. Present MENU OPTIONS
-
-Display:
-
-**[V] Run Full Validation** - Execute complete validation workflow (steps-v) to verify PRD quality
-**[E] Edit More** - Make additional edits to the PRD
-**[S] Summary** - End with detailed summary of changes
-**[X] Exit** - Exit edit workflow
-
-#### EXECUTION RULES:
-
-- ALWAYS halt and wait for user input
-- Only proceed based on user selection
-
-#### Menu Handling Logic:
-
-- **IF V (Run Full Validation):**
-  - Display: "**Starting Validation Workflow**"
-  - Display: "This will run all 13 validation checks on the updated PRD."
-  - Display: "Preparing to validate: {prd_file_path}"
-  - Display: "**Proceeding to validation...**"
-  - Read fully and follow: {validationWorkflow} (steps-v/step-v-01-discovery.md)
-  - Note: This hands off to the validation workflow which will run its complete 13-step process
-
-- **IF E (Edit More):**
-  - Display: "**Additional Edits**"
-  - Ask: "What additional edits would you like to make?"
-  - Accept input, then display: "**Returning to edit step...**"
-  - Read fully and follow: `./step-e-03-edit.md` again
-
-- **IF S (Summary):**
-  - Display detailed summary including:
-    - Complete list of all changes made
-    - Before/after comparison (key improvements)
-    - Recommendations for next steps
-  - Display: "**Edit Workflow Complete**"
-  - Exit
-
-- **IF X (Exit):**
-  - Display summary
-  - Display: "**Edit Workflow Complete**"
-  - Exit
-
-- **IF Any other:** Help user, then redisplay menu
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Complete edit summary compiled accurately
-- All changes clearly documented
-- Options presented with clear expectations
-- Validation option seamlessly integrates with steps-v workflow
-- User can validate, edit more, or exit
-- Clean handoff to validation workflow (if chosen)
-- Edit workflow completes properly
-
-### ❌ SYSTEM FAILURE:
-
-- Missing changes in summary
-- Not offering validation option
-- Not documenting completion properly
-- No clear handoff to validation workflow
-
-**Master Rule:** Edit workflow seamlessly integrates with validation. User can edit → validate → edit again → validate again in iterative improvement cycle.