wogiflow 1.0.21 → 1.0.22

package/.claude/commands/wogi-roadmap.md

@@ -0,0 +1,241 @@
+# /wogi-roadmap - Roadmap Management
+
+View and manage the project roadmap for deferred work and future phases.
+
+## Usage
+
+```
+/wogi-roadmap                    # Show roadmap summary
+/wogi-roadmap add "title"        # Add item to roadmap
+/wogi-roadmap validate "title"   # Validate dependencies before implementing
+/wogi-roadmap promote "title"    # Move item to ready.json as a story
+```
+
+## When to Use
+
+- **View deferred work**: See what's planned for later
+- **Add deferred phases**: When breaking large features into phases
+- **Before implementing**: Validate dependencies are still valid
+- **Promote to active**: When ready to implement a deferred item
+
+## Steps
+
+### Show Roadmap (Default)
+
+1. Read `.workflow/roadmap.md`
+2. Parse phases: Now, Next, Later, Ideas, Completed
+3. Display summary with item counts per phase
+4. Show dependencies for items in Later phase
+
+**Output format:**
+```
+==================================================
+        Project Roadmap
+==================================================
+
+> Now (Current Focus) (2)
+    Authentication system ← Phase 0: Setup
+    User profile page
+
+- Next (Ready to Plan) (3)
+    Password reset flow ← Phase 1: Auth
+    Email verification
+    OAuth integration ← Phase 1: Auth
+
+o Later (Future Phases) (4)
+    Two-factor auth ← Phase 2: Security
+    Session management ← Phase 2: Security
+    API rate limiting
+    Audit logging ← Phase 3: Compliance
+
+? Ideas (Exploration) (1)
+    Single sign-on
+
+File: .workflow/roadmap.md
+Commands: add, validate, promote, move
+```
+
+### Add Item
+
+When user runs `/wogi-roadmap add "Feature name"`:
+
+1. Parse optional flags:
+   - `--phase=<now|next|later|ideas>` (default: later)
+   - `--depends="Parent phase"`
+   - `--assumes="assumption1, assumption2"`
+   - `--files="path/to/file.ts, other/file.ts"`
+
+2. Create item block:
+```markdown
+### [Feature Name]
+
+**Status:** Deferred
+**Created:** [TODAY]
+**Depends On:** [from --depends or ask user]
+
+**Assumes:**
+- [from --assumes or ask user]
+
+**Key Files:**
+- [from --files or ask user]
+
+**Context When Deferred:**
+[Ask user or infer from current work]
+
+**Implementation Plan:**
+1. [Ask user]
+```
+
+3. Insert into appropriate phase section in `.workflow/roadmap.md`
+
+4. Confirm: "Added '[Feature]' to [phase] phase"
+
+### Validate Item
+
+When user runs `/wogi-roadmap validate "Feature name"`:
+
+1. Find the item in roadmap.md
+2. Check each dependency:
+
+   **Depends On:**
+   - Is parent phase/feature marked complete?
+   - Check both roadmap.md (Completed section) and ready.json (recentlyCompleted)
+
+   **Key Files:**
+   - Do the listed files still exist?
+   - (Advanced) Do they still have expected exports/interfaces?
+
+   **Assumes:**
+   - Flag assumptions for AI review
+   - Look for contradicting patterns in codebase
+
+3. Report results:
+
+**If valid:**
+```
+Validating: OAuth integration
+
++ All dependencies valid
++ Ready to implement
+```
+
+**If issues found:**
+```
+Validating: OAuth integration
+
+Issues (blocking):
+  - Key file not found: src/auth/jwt.ts
+
+Warnings (review recommended):
+  - Dependency not marked complete: Phase 1: Auth
+  - Assumption needs verification: Using JWT tokens
+
+Cannot proceed until issues are resolved.
+```
+
+### Promote Item
+
+When user runs `/wogi-roadmap promote "Feature name"`:
+
+1. Validate the item first (run validate step)
+2. If validation fails, show issues and ask to proceed anyway
+3. If valid (or user confirms):
+   - Extract implementation plan
+   - Run `/wogi-story "[Feature name]"` to create story
+   - Move item to "Completed" section in roadmap
+   - Add note: "Promoted to story on [DATE]"
+
+### Move Item
+
+When user runs `/wogi-roadmap move "Feature" --to=next`:
+
+1. Find item in current phase
+2. Remove from current location
+3. Insert into target phase
+4. Confirm: "Moved '[Feature]' from [old] to [new]"
+
+## AI Behavior Integration
+
+### When User Requests Large Feature
+
+If you detect a request that would require 5+ tasks or multiple phases:
+
+1. Break down into phases
+2. Present breakdown to user
+3. If user agrees to defer later phases:
+   ```javascript
+   // For each deferred phase:
+   const item = {
+     title: "Phase N: Feature description",
+     dependsOn: "Phase N-1: Previous phase",
+     assumes: [
+       "Key assumption from current implementation",
+       "Another architectural decision"
+     ],
+     keyFiles: [
+       "src/relevant/file.ts - Contains X interface",
+       "src/other/file.ts - Has Y dependency"
+     ],
+     context: "Current state description",
+     plan: ["Step 1", "Step 2", "Step 3"]
+   };
+
+   // Add to roadmap
+   const { addItem } = require('./scripts/flow-roadmap');
+   addItem(item, 'later');
+   ```
+
+4. Inform user: "Added N items to your roadmap. Run `/wogi-roadmap` to see them."
+
+### When Modifying Key Files
+
+Before modifying any file, check if it's listed in roadmap items:
+
+```javascript
+const { parseRoadmap } = require('./scripts/flow-roadmap');
+const roadmap = parseRoadmap();
+
+// Collect all key files from all phases
+const keyFiles = [];
+for (const [phase, items] of Object.entries(roadmap.phases)) {
+  for (const item of items) {
+    if (item.keyFiles) {
+      keyFiles.push(...item.keyFiles.map(f => ({
+        file: f,
+        item: item.title,
+        phase
+      })));
+    }
+  }
+}
+
+// Check if target file is in list
+const affected = keyFiles.filter(k =>
+  k.file.includes(targetFile) || targetFile.includes(k.file.split(' - ')[0])
+);
+
+if (affected.length > 0) {
+  // Warn user
+}
+```
+
+## If Roadmap Doesn't Exist
+
+```
+No roadmap found for this project.
+
+Would you like me to create one? This helps track:
+- Deferred work from large features
+- Future phases and their dependencies
+- Ideas for later exploration
+
+[Yes, create roadmap] [No thanks]
+```
+
+If yes, copy template from `templates/roadmap.md` to `.workflow/roadmap.md`.
+
+## Related Commands
+
+- `/wogi-story` - Create detailed story with acceptance criteria
+- `/wogi-ready` - View tasks ready to implement
+- `/wogi-status` - Overall project status

package/.claude/commands/wogi-rules.md

@@ -0,0 +1,104 @@
+View and manage project coding rules.
+
+Usage:
+- `/wogi-rules` - List all rules
+- `/wogi-rules [name]` - View specific rule
+- `/wogi-rules sync` - Sync decisions.md to .claude/rules/
+
+## How Rules Work (v2.1.0)
+
+Rules are **auto-generated** from `.workflow/state/decisions.md`:
+
+```
+decisions.md (Source of Truth)     .claude/rules/ (Auto-Generated)
+  ├── ## Component Architecture   →  component-architecture.md
+  ├── ## Coding Standards         →  coding-standards.md
+  ├── ## API Patterns             →  api-patterns.md
+  └── ## 2026-01-02               →  2026-01-02.md
+```
+
+**Key Points:**
+- Edit `decisions.md` to add/change rules
+- `.claude/rules/` is auto-generated (don't edit directly)
+- Rules sync automatically when decisions.md changes
+- Path-scoped rules only load when working on relevant files
+
+## Manual Sync
+
+If rules seem out of date:
+```bash
+node scripts/flow-rules-sync.js
+```
+
+Or use this command:
+```
+/wogi-rules sync
+```
+
+## Path Scoping
+
+Rules are automatically scoped based on section keywords:
+
+| Keyword in Section | Files Loaded For |
+|--------------------|------------------|
+| component, ui | `src/components/**/*` |
+| api, backend | `src/api/**/*` |
+| test, testing | `**/*.{test,spec}.*` |
+| style, css | `**/*.{css,scss}` |
+| database, entity | `src/**/*.entity.*` |
+
+## Output - List
+
+```
+Project Rules
+
+Source: .workflow/state/decisions.md
+
+Generated Rules (.claude/rules/):
+  - component-architecture.md (paths: src/components/**/*)
+  - coding-standards.md
+  - api-patterns.md (paths: src/api/**/*)
+  - 2026-01-02.md
+
+Last synced: 2026-01-08
+
+Use: /wogi-rules [name] to view a rule
+     /wogi-rules sync to regenerate rules
+```
+
+## Adding Rules
+
+To add a new rule:
+
+1. Add a new `## Section` to decisions.md:
+   ```markdown
+   ## API Validation
+
+   - All API endpoints must validate input
+   - Use Zod schemas for request validation
+   - Return 400 for validation errors
+   ```
+
+2. Rules auto-sync on next decisions.md update, or run:
+   ```
+   /wogi-rules sync
+   ```
+
+## Execution
+
+When user runs `/wogi-rules`:
+
+1. List rules in `.claude/rules/`
+2. Show source (decisions.md)
+3. Show path scoping for each rule
+4. Show last sync time
+
+When user runs `/wogi-rules sync`:
+
+1. Run `node scripts/flow-rules-sync.js`
+2. Show updated rules
+
+When user runs `/wogi-rules [name]`:
+
+1. Read `.claude/rules/[name].md`
+2. Display content

package/.claude/commands/wogi-search.md

@@ -0,0 +1,33 @@
+Search the request log by tag or keyword. Provide search term: `/wogi-search #screen:login`
+
+Search `.workflow/state/request-log.md` for:
+- Tags: `#screen:name`, `#component:name`, `#feature:name`, `#bug:id`
+- Keywords: Any text in request or result fields
+
+Output matching entries with context:
+```
+🔍 Search: #screen:login
+
+Found 3 entries:
+
+R-045 | 2024-01-15 14:32
+Type: change
+Tags: #screen:login #component:AuthForm
+Request: "Add forgot password link"
+Result: Added link, routes to /forgot-password
+Files: LoginScreen.tsx, routes.ts
+
+R-038 | 2024-01-14 09:15
+Type: fix
+Tags: #screen:login #bug:BUG-003
+Request: "Fix password visibility toggle"
+Result: Fixed icon state, added aria-label
+Files: LoginForm.tsx
+
+R-032 | 2024-01-13 11:20
+Type: new
+Tags: #screen:login
+Request: "Create login screen"
+Result: Basic login form with email/password
+Files: LoginScreen.tsx, LoginForm.tsx
+```

package/.claude/commands/wogi-session-end.md

@@ -0,0 +1,49 @@
+Properly end a work session.
+
+Steps:
+1. **Check request-log** - Ensure all changes are logged
+2. **Check log size** - If over 50 entries, suggest archiving
+3. **Check app-map** - If new components created, verify they're added
+4. **Update progress.md** - Add handoff notes for next session
+5. **Commit changes** - Stage and commit all workflow files
+6. **Offer to push** - Ask if should push to remote
+
+Output:
+```
+📤 Ending Session
+
+Checking request-log...
+  ✓ 3 entries added today
+  ⚠ Log has 67 entries - consider: ./scripts/flow archive --keep 50
+
+Checking app-map...
+  ✓ 1 new component added (ProfileCard)
+
+Updating progress.md...
+  Added handoff notes
+
+Committing...
+  ✓ Committed: "chore: End session - 3 changes logged"
+
+Push to remote? (y/n)
+```
+
+Progress.md handoff format:
+```markdown
+## Session End: 2024-01-15 17:30
+
+### Completed
+- TASK-012: Forgot password link
+- Fixed BUG-004
+
+### In Progress
+- TASK-015: User profile (70% done)
+
+### Next Session
+- Finish profile page styling
+- Start TASK-018
+
+### Notes
+- API endpoint for preferences not ready yet
+- Decided to use shadcn/ui for modal
+```

package/.claude/commands/wogi-setup-stack.md

@@ -0,0 +1,151 @@
+Interactive tech stack wizard that configures your project and generates skills.
+
+Usage:
+- `/wogi-setup-stack` - Run interactive wizard
+- `/wogi-setup-stack --fetch-docs` - Fetch documentation for existing skills via Context7
+- `/wogi-setup-stack --regenerate` - Regenerate skills from saved selections
+
+## What This Does
+
+1. **Interactive Wizard** - Guides you through selecting:
+   - Project type (web, mobile, backend, full-stack, CLI, library)
+   - Frontend framework (React, Next.js, Vue, Svelte, Angular, etc.)
+   - Backend framework (Express, NestJS, FastAPI, Django, etc.)
+   - State management (Redux, Zustand, TanStack Query, Pinia, etc.)
+   - Styling (Tailwind, CSS Modules, Styled Components, etc.)
+   - Database & ORM (PostgreSQL, MongoDB, Prisma, etc.)
+   - Testing (Jest, Vitest, Playwright, Cypress, etc.)
+   - Additional tools (Docker, GraphQL, Auth, etc.)
+
+2. **"Choose Best For Me"** - Enter `?` at any prompt for recommended defaults:
+   - Frontend: Next.js
+   - State: TanStack Query + Zustand
+   - Styling: Tailwind + shadcn/ui
+   - Backend: NestJS (TS) or FastAPI (Python)
+   - Database: PostgreSQL + Prisma
+   - Testing: Vitest + Playwright
+
+3. **Skills Generation** - Creates skill files for each technology:
+   - `skill.md` - Overview and when to apply
+   - `knowledge/patterns.md` - Best practices
+   - `knowledge/anti-patterns.md` - Common mistakes
+   - `rules/conventions.md` - Coding standards
+
+4. **Skills Index** - Creates `.claude/skills/skills-index.json` for easy access
+
+5. **Updates**:
+   - Adds tech stack to `decisions.md`
+   - Updates `config.json` with installed skills
+
+## Running the Wizard
+
+```bash
+# Via Claude Code command
+/wogi-setup-stack
+
+# Or directly
+node scripts/flow-stack-wizard.js
+```
+
+## Output
+
+```
+============================================================
+  Tech Stack Wizard
+  Configure your project and generate coding patterns
+============================================================
+
+What type of project is this?
+  (1) Web Application
+  (2) Mobile App (React Native / Flutter / Native)
+  ...
+
+Your choice: 5
+
+What's your focus?
+  (1) Frontend only
+  (2) Backend only
+  (3) Full-stack (both)
+
+Your choice: 3
+
+...
+
+============================================================
+  Your Tech Stack
+============================================================
+
+  Project Type: Full-Stack (Frontend + Backend)
+  Frontend: Next.js
+  State Management: TanStack Query (server state)
+  Styling: shadcn/ui + Tailwind
+  Backend: NestJS
+  Database: Prisma
+
+Generate skills and fetch documentation? [Y/n] y
+
+  Generating skills for:
+    - Next.js
+    - TanStack Query
+    - Tailwind CSS
+    - NestJS
+    - Prisma
+
+  Processing Next.js...
+    ✓ Created: .claude/skills/nextjs
+
+  ...
+
+  ✓ Created: .claude/skills/skills-index.json
+  ✓ Updated: .workflow/state/decisions.md
+  ✓ Updated: .workflow/config.json
+
+✓ Skills generated successfully!
+```
+
+## Fetching Documentation
+
+After running the wizard, populate skills with real documentation:
+
+```
+/wogi-setup-stack --fetch-docs
+```
+
+This uses Context7 MCP to fetch latest docs and extract:
+- Best practices
+- Common patterns
+- Anti-patterns
+- Code examples
+
+## Skills Index Structure
+
+```json
+{
+  "version": "1.0",
+  "generated": "2024-01-06T12:00:00Z",
+  "skills": {
+    "nextjs": {
+      "path": ".claude/skills/nextjs/",
+      "covers": ["next.js", "app router", "server components"],
+      "sections": {
+        "patterns": "knowledge/patterns.md",
+        "anti-patterns": "knowledge/anti-patterns.md"
+      }
+    }
+  },
+  "projectStack": ["nextjs", "tailwind", "prisma"]
+}
+```
+
+## Re-running the Wizard
+
+You can run the wizard again to:
+- Add new technologies
+- Change existing selections
+- Regenerate skills with updated documentation
+
+Existing learnings in `knowledge/learnings.md` are preserved.
+
+## Integration
+
+Run `/wogi-setup-stack` anytime after installing WogiFlow to configure your tech stack.

package/.claude/commands/wogi-skill-learn.md

@@ -0,0 +1,66 @@
+---
+description: Manually trigger skill learning extraction from recent changes
+---
+
+# Skill Learning
+
+This command extracts learnings from recent work and updates relevant skills.
+
+## What It Does
+
+1. Analyzes changed files (staged or recent commits)
+2. Matches files to installed skills by pattern
+3. Updates skill knowledge files:
+   - `knowledge/learnings.md` - What was done
+   - `knowledge/patterns.md` - What worked (on success)
+   - `knowledge/anti-patterns.md` - What to avoid (on errors)
+4. Logs unmatched files to `feedback-patterns.md`
+
+## When to Use
+
+This runs automatically on:
+- **Pre-commit hook** (if hooks enabled)
+- **Session end** (`/wogi-session-end`)
+- **Context compaction** (`/wogi-compact`)
+
+Use this command manually when:
+- You want to extract learnings mid-session
+- After fixing a significant bug
+- After discovering a new pattern
+
+## Execute
+
+```bash
+# Manual extraction from current changes
+node scripts/flow-skill-learn.js --trigger=manual
+
+# Target specific skill
+node scripts/flow-skill-learn.js --skill=nestjs
+
+# Preview without making changes
+node scripts/flow-skill-learn.js --dry-run --verbose
+```
+
+## Configuration
+
+Skill learning is controlled by `config.json`:
+
+```json
+{
+  "skillLearning": {
+    "enabled": true,
+    "autoExtract": true,
+    "triggers": {
+      "onCommit": true,
+      "onTaskComplete": true,
+      "onCompact": true
+    }
+  }
+}
+```
+
+## Related Commands
+
+- `/wogi-skills` - List installed skills
+- `/wogi-skill-create` - Create a new skill
+- `/wogi-session-end` - End session (includes learning extraction)