vibe-fabric 0.3.2 → 0.4.0

package/.claude/prompts/prd/task-fix-format.md

@@ -0,0 +1,102 @@
+# Fix PRD Format Issues
+
+## Variables
+
+| Variable | Description | Required |
+|----------|-------------|----------|
+| {PROJECT_PATH} | Path to the project directory | Yes |
+| {OUTPUT_FILE} | Path to write task output | Yes |
+| {TASK_NAME} | Name of this task | Yes |
+| {TASK_DESCRIPTION} | Description of what to fix | Yes |
+| {ISSUES} | JSON array of issues to fix | Yes |
+
+---
+
+## Context
+
+You are fixing format issues in PRD files.
+
+Project: {PROJECT_PATH}
+Task: {TASK_NAME}
+
+Issues to fix:
+{ISSUES}
+
+---
+
+## Your Task
+
+Fix the identified format issues in the PRD files.
+
+### Common Fixes
+
+1. **Missing priority field**
+   - Add `| **Priority** | P1 |` to metadata table
+   - Use P0 for critical, P1 for high, P2 for normal, P3 for low
+
+2. **Invalid requirement ID**
+   - Rename to format: `REQ-MODULE-NNN`
+   - Example: `REQ-AUTH-001`, `REQ-USER-002`
+
+3. **Missing status field**
+   - Add `| **Status** | draft |` to metadata table
+   - Valid statuses: draft, in_progress, implemented, deprecated
+
+4. **Invalid AC format**
+   - Convert to: "Given [context], when [action], then [result]"
+   - Example: "Given valid credentials, when user submits login, then session is created"
+
+5. **Missing module field**
+   - Add `| **Module** | module-name |` to metadata table
+
+### Step 1: Read Files
+
+Read each file that needs fixing.
+
+### Step 2: Apply Fixes
+
+Make the minimum changes needed to fix each issue.
+
+### Step 3: Write Changes
+
+Write the corrected files back.
+
+---
+
+## Output Format
+
+Write to: {OUTPUT_FILE}
+
+```json
+{
+  "task": "fix-format",
+  "status": "complete",
+  "fixes": [
+    {
+      "file": "docs/prd/modules/auth/login.md",
+      "issue": "Missing priority field",
+      "fix": "Added priority: P1"
+    },
+    {
+      "file": "docs/prd/modules/users/profile.md",
+      "issue": "Invalid AC format",
+      "fix": "Converted AC-1 to Given/When/Then format"
+    }
+  ],
+  "files_modified": [
+    "docs/prd/modules/auth/login.md",
+    "docs/prd/modules/users/profile.md"
+  ]
+}
+```
+
+---
+
+## Rules
+
+- Make MINIMUM changes to fix issues
+- Do NOT change content meaning
+- Do NOT add new requirements
+- Do NOT reformat entire files
+- Preserve existing formatting where possible
+- If unsure about a fix, skip it and note in output

package/.claude/prompts/prd/task-update-status.md

@@ -0,0 +1,89 @@
+# Update PRD Requirement Statuses
+
+## Variables
+
+| Variable | Description | Required |
+|----------|-------------|----------|
+| {PROJECT_PATH} | Path to the project directory | Yes |
+| {OUTPUT_FILE} | Path to write task output | Yes |
+| {TASK_NAME} | Name of this task | Yes |
+| {TASK_DESCRIPTION} | Description of what to update | Yes |
+| {UPDATES} | JSON array of status updates to make | Yes |
+
+---
+
+## Context
+
+You are updating requirement statuses based on completed scopes.
+
+Project: {PROJECT_PATH}
+Task: {TASK_NAME}
+
+Updates to make:
+{UPDATES}
+
+---
+
+## Your Task
+
+Update requirement statuses in PRD files based on completed scope work.
+
+### Step 1: Verify Completion
+
+For each update, verify the scope is in `docs/scopes/completed/`.
+
+### Step 2: Update Status
+
+Change the status field in the requirement's metadata table:
+- From: `| **Status** | draft |`
+- To: `| **Status** | implemented |`
+
+### Step 3: Add Coverage Reference
+
+Update the "Covered By" field if present:
+- `| **Covered By** | SCOPE-001 |`
+
+Or add it if missing.
+
+---
+
+## Output Format
+
+Write to: {OUTPUT_FILE}
+
+```json
+{
+  "task": "update-status",
+  "status": "complete",
+  "updates": [
+    {
+      "requirement": "REQ-AUTH-001",
+      "file": "docs/prd/modules/auth/login.md",
+      "old_status": "draft",
+      "new_status": "implemented",
+      "scope": "SCOPE-001"
+    },
+    {
+      "requirement": "REQ-AUTH-002",
+      "file": "docs/prd/modules/auth/registration.md",
+      "old_status": "draft",
+      "new_status": "implemented",
+      "scope": "SCOPE-001"
+    }
+  ],
+  "files_modified": [
+    "docs/prd/modules/auth/login.md",
+    "docs/prd/modules/auth/registration.md"
+  ]
+}
+```
+
+---
+
+## Rules
+
+- Only update status if scope is truly completed
+- Do NOT change any other content
+- Preserve file formatting
+- If requirement file not found, skip and note in output
+- If status already correct, skip (no update needed)

package/.claude/prompts/scope/assess.md

@@ -0,0 +1,201 @@
+# Scope Assessment
+
+## Variables
+
+| Variable | Description | Required |
+|----------|-------------|----------|
+| {PROJECT_PATH} | Path to the project directory | Yes |
+| {OUTPUT_FILE} | Path to write the assessment output | Yes |
+
+---
+
+## Context
+
+You are helping create implementation scopes from a Product Requirements Document (PRD).
+
+Project: {PROJECT_PATH}
+
+A scope is a self-contained work package that:
+- Derives from PRD requirements
+- Can be sent to a development repository
+- Contains everything needed for implementation
+- Has clear acceptance criteria
+
+---
+
+## Your Task
+
+Analyze the PRD and help the user create scopes.
+
+### Step 1: Analyze Current State
+
+Read and analyze:
+- `docs/prd/modules/` - All requirement modules
+- `docs/scopes/drafts/` - Existing draft scopes
+- `docs/scopes/ready/` - Approved scopes waiting to send
+- `docs/scopes/sent/` - Scopes already sent to dev repos
+- `docs/scopes/completed/` - Completed scopes
+
+Identify:
+- **Unscoped requirements**: Requirements not covered by any scope
+- **Existing drafts**: Scopes that may need review
+- **Dependencies**: Requirements that depend on others
+- **Priority order**: Which requirements should be scoped first
+
+### Step 2: Present Findings
+
+Summarize your findings clearly:
+- Total requirements in PRD
+- Scopeable requirements (not yet covered)
+- Existing draft scopes
+- Recommended scope order based on dependencies
+
+### Step 3: Ask User Intent
+
+Ask the user: **"What would you like to do?"**
+
+Present options:
+1. **Create new scope** - Start a new scope from PRD requirements
+2. **Review existing draft** - Improve an existing draft scope
+3. **Check coverage** - See which requirements need scopes
+4. **Just checking** - Show summary only
+
+Listen for specific requirements they want to scope (e.g., "scope the auth feature").
+
+### Step 4: Create Task List
+
+Based on findings and user intent, create a list of tasks:
+
+**Task Types:**
+- `task-analyze-prd` - Categorize requirements by priority (non-interactive)
+- `task-recommend` - Recommend scope boundaries (non-interactive)
+- `task-create-scope` - Create scope through Q&A (interactive)
+- `task-review-scope` - Review existing scope (interactive)
+- `task-validate` - Validate scope format (non-interactive)
+- `task-check-deps` - Check dependency ordering (non-interactive)
+
+---
+
+## Output Format
+
+Write to: {OUTPUT_FILE}
+
+```json
+{
+  "complexity": "S|M|L",
+  "assessment": {
+    "prd_exists": true,
+    "module_count": 5,
+    "requirement_count": 23,
+    "unscoped_count": 15,
+    "draft_scopes": 2,
+    "ready_scopes": 1,
+    "sent_scopes": 3,
+    "completed_scopes": 2,
+    "user_intent": "create scope for auth feature"
+  },
+  "tasks": [
+    {
+      "id": 1,
+      "name": "analyze-requirements",
+      "description": "Analyze and categorize PRD requirements",
+      "prompt": "task-analyze-prd",
+      "interactive": false,
+      "context": {
+        "modules": ["auth", "users", "payments"]
+      }
+    },
+    {
+      "id": 2,
+      "name": "recommend-scope",
+      "description": "Recommend scope boundaries for auth feature",
+      "prompt": "task-recommend",
+      "interactive": false,
+      "context": {
+        "target_feature": "auth",
+        "requirements": ["REQ-AUTH-001", "REQ-AUTH-002"]
+      }
+    },
+    {
+      "id": 3,
+      "name": "create-auth-scope",
+      "description": "Create scope for authentication feature",
+      "prompt": "task-create-scope",
+      "interactive": true,
+      "context": {
+        "feature": "auth",
+        "requirements": ["REQ-AUTH-001", "REQ-AUTH-002"],
+        "suggested_id": "SCOPE-001"
+      }
+    },
+    {
+      "id": 4,
+      "name": "validate-scope",
+      "description": "Validate scope format and completeness",
+      "prompt": "task-validate",
+      "interactive": false,
+      "context": {
+        "scope_id": "SCOPE-001"
+      }
+    }
+  ]
+}
+```
+
+---
+
+## Rules
+
+- Focus ONLY on scope creation and management
+- Maximum 6 tasks (group related work if needed)
+- Always include validate task for new scopes
+- Recommend scoping in dependency order (dependencies first)
+- Be concise in your analysis - don't overwhelm the user
+- If user says "just checking", output empty tasks array
+- If no PRD requirements exist, suggest user runs `vibe prd` first
+
+---
+
+## Scope ID Convention
+
+New scopes should use format: `SCOPE-XXX`
+- Check existing scopes to determine next number
+- Examples: SCOPE-001, SCOPE-002, SCOPE-003
+
+---
+
+## Examples
+
+**User says "just checking":**
+```json
+{
+  "complexity": "S",
+  "assessment": {...},
+  "tasks": []
+}
+```
+
+**User says "create a scope for payments":**
+```json
+{
+  "complexity": "M",
+  "assessment": {...},
+  "tasks": [
+    {"id": 1, "name": "analyze-requirements", "prompt": "task-analyze-prd", "interactive": false, ...},
+    {"id": 2, "name": "recommend-payments", "prompt": "task-recommend", "interactive": false, ...},
+    {"id": 3, "name": "create-payments-scope", "prompt": "task-create-scope", "interactive": true, ...},
+    {"id": 4, "name": "validate-scope", "prompt": "task-validate", "interactive": false, ...}
+  ]
+}
+```
+
+**User says "review SCOPE-001":**
+```json
+{
+  "complexity": "S",
+  "assessment": {...},
+  "tasks": [
+    {"id": 1, "name": "review-scope-001", "prompt": "task-review-scope", "interactive": true, "context": {"scope_id": "SCOPE-001"}}
+  ]
+}
+```

package/.claude/prompts/scope/synthesize.md

@@ -0,0 +1,270 @@
+# Scope Synthesis and Approval
+
+## Variables
+
+| Variable | Description | Required |
+|----------|-------------|----------|
+| {PROJECT_PATH} | Path to the project directory | Yes |
+| {TASK_OUTPUTS} | JSON array of task output file paths | Yes |
+| {TOTAL_TASKS} | Number of tasks completed | Yes |
+
+---
+
+## Context
+
+You are reviewing all work from the scope operation and getting user approval.
+
+Project: {PROJECT_PATH}
+Task outputs: {TASK_OUTPUTS}
+Total tasks: {TOTAL_TASKS}
+
+---
+
+## Your Task
+
+Present all scope changes for user approval and apply approved changes.
+
+### Step 1: Load All Task Outputs
+
+Read each file in {TASK_OUTPUTS} and combine the results.
+
+### Step 2: Present Summary
+
+Show what was created or modified:
+
+```
++======================================================================+
+|                        SCOPE CHANGES TO APPLY                         |
++======================================================================+
+
+  NEW SCOPES (1)
+  ----------------------------------------------------------------
+  SCOPE-003: User Authentication
+    Target:     backend
+    Complexity: M
+    Priority:   P1
+    Requirements: 4
+    Acceptance Criteria: 8
+
+    Summary: Implement JWT-based authentication with login,
+    logout, and token refresh endpoints.
+
+    File: docs/scopes/drafts/SCOPE-003-user-authentication.md
+
+  UPDATED SCOPES (1)
+  ----------------------------------------------------------------
+  SCOPE-001: Dashboard Analytics (reviewed)
+    Changes:
+      - Refined acceptance criteria (3 updated)
+      - Added dependency on SCOPE-002
+      - Fixed format issues
+
+    File: docs/scopes/drafts/SCOPE-001-dashboard-analytics.md
+
+  VALIDATION RESULTS
+  ----------------------------------------------------------------
+  All scopes pass validation:
+    [x] SCOPE-003: Valid ID format
+    [x] SCOPE-003: Has required fields
+    [x] SCOPE-003: AC uses Given/When/Then
+    [x] SCOPE-003: Linked to PRD requirements
+
++======================================================================+
+```
+
+### Step 3: Get User Decision
+
+Ask user:
+- **"Approve"** - Save scope to drafts folder
+- **"Approve and move to ready"** - Save and move to ready/ (approved for sending)
+- **"Edit"** - Let user request specific changes
+- **"Discard"** - Don't save any changes
+
+### Step 4: Apply Approved Changes
+
+For approved scopes:
+1. Write scope file to appropriate directory
+2. Create `docs/scopes/ready/` directory if needed
+3. Update coverage tracking if applicable
+
+For "Approve and move to ready":
+1. Write to `docs/scopes/ready/` instead of drafts
+2. Update scope status to "approved" in the file
+
+### Step 5: Generate Summary
+
+After applying changes:
+- List all files created
+- List all files modified
+- Show next steps
+
+---
+
+## Output Format
+
+No file output needed - changes are applied directly to scope files.
+
+Display to user:
+```
+Applied changes:
+  - Created: docs/scopes/drafts/SCOPE-003-user-authentication.md
+  - Modified: docs/scopes/drafts/SCOPE-001-dashboard-analytics.md
+
+Next steps:
+  - Review scopes: vibe scope --check
+  - Send to repo: vibe send SCOPE-003
+  - Continue working: vibe scope
+```
+
+---
+
+## Rules
+
+- NEVER apply changes without user approval
+- If user says "discard", don't write ANY files
+- If user says "edit", enter refinement conversation
+- Always validate scope format before saving
+- Use proper directory structure
+- File naming: `SCOPE-XXX-slug-title.md`
+
+---
+
+## Scope File Structure
+
+When writing scope files:
+
+**File naming:**
+`SCOPE-XXX-kebab-case-title.md`
+
+Example: `SCOPE-003-user-authentication.md`
+
+**Directory structure:**
+```
+docs/scopes/
+├── drafts/           # Work in progress (default)
+├── ready/            # Approved, waiting to send
+├── sent/             # Sent to dev repos
+└── completed/        # Implementation done
+```
+
+---
+
+## Scope Template
+
+Use this template when writing scope files:
+
+```markdown
+# SCOPE-XXX: [Feature Title]
+
+## Metadata
+
+| Field | Value |
+|-------|-------|
+| **ID** | `SCOPE-XXX` |
+| **Status** | `draft` |
+| **Target** | `frontend` / `backend` / `both` |
+| **Complexity** | `S` / `M` / `L` / `XL` |
+| **Module** | `[requirement-module-name]` |
+| **Priority** | `P1` / `P2` / `P3` |
+
+---
+
+## Summary
+
+[2-3 sentences describing what this scope delivers and why it matters]
+
+---
+
+## User Story
+
+As a [role/persona],
+I want to [action/capability],
+so that [benefit/value].
+
+---
+
+## Requirements
+
+### Functional Requirements
+
+- **REQ-1:** [Requirement from PRD]
+- **REQ-2:** [Requirement from PRD]
+
+### Non-Functional Requirements
+
+- **NFR-1:** [Performance, security, etc.]
+
+---
+
+## Acceptance Criteria
+
+- **AC-1:** Given [context], when [action], then [expected result]
+- **AC-2:** Given [context], when [action], then [expected result]
+
+---
+
+## Technical Constraints
+
+- **C-1:** [Constraint]
+
+---
+
+## Dependencies
+
+| Scope | Reason | Blocking |
+|-------|--------|----------|
+| SCOPE-XXX | [Why needed] | Yes/No |
+
+---
+
+## Out of Scope
+
+- [Explicit exclusion]
+- [Explicit exclusion]
+
+---
+
+## Implementation Notes
+
+### Suggested Approach
+
+[Optional guidance]
+
+### Key Files/Modules
+
+- `path/to/relevant/file.ts`
+
+---
+
+## Review Checklist
+
+- [ ] Summary is accurate and concise
+- [ ] All requirements have acceptance criteria
+- [ ] Acceptance criteria are testable
+- [ ] Dependencies identified
+- [ ] Out of scope documented
+```
+
+---
+
+## Approval Flow
+
+```
+User approves as draft
+    → Write to docs/scopes/drafts/
+    → Status: draft
+
+User approves and moves to ready
+    → Write to docs/scopes/ready/
+    → Status: approved
+
+User requests edits
+    → Enter refinement loop
+    → Ask what to change
+    → Make changes
+    → Present again
+
+User discards
+    → Don't write anything
+    → Clean up any temp files
+```