viepilot 1.0.0

package/skills/vp-pause/SKILL.md

@@ -0,0 +1,150 @@
+---
+name: vp-pause
+description: "Pause work với context preservation để resume sau"
+version: 0.1.0
+---
+
+<cursor_skill_adapter>
+## A. Skill Invocation
+- Skill được gọi khi user mention `vp-pause`, `/vp-pause`, "pause", "dừng", "tạm nghỉ"
+- Treat all user text after the skill mention as `{{VP_ARGS}}`
+
+## B. User Prompting
+Prompt user conversationally để gather state info.
+
+## C. Tool Usage
+Use Cursor tools: `Shell`, `ReadFile`, `Glob`, `rg`, `ApplyPatch`, `WebSearch`, `WebFetch`, `Subagent`
+</cursor_skill_adapter>
+
+<objective>
+Save complete work state để có thể resume từ bất kỳ context nào.
+
+**Creates/Updates:**
+- `.viepilot/HANDOFF.json` - Machine-readable state
+- `.viepilot/phases/{current}/.continue-here.md` - Human-readable context
+- Git WIP commit
+
+**After:** Safe to close session. Resume với `/vp-resume`
+</objective>
+
+<execution_context>
+@$HOME/.cursor/viepilot/workflows/pause-work.md
+</execution_context>
+
+<process>
+Execute workflow from `@$HOME/.cursor/viepilot/workflows/pause-work.md`
+
+### Step 1: Detect Current Position
+```bash
+# Find current phase from TRACKER.md or recent files
+Read TRACKER.md → current_phase, current_task
+Check PHASE-STATE.md → task status
+```
+
+### Step 2: Gather State
+Collect:
+1. **Current position**: Phase, task, line
+2. **Work completed**: What got done this session
+3. **Work remaining**: What's left
+4. **Decisions made**: Key decisions and rationale
+5. **Blockers/issues**: Anything stuck
+6. **Human actions pending**: Manual interventions needed
+7. **Background processes**: Running servers/watchers
+8. **Uncommitted files**: Changes not yet committed
+
+Ask user for clarifications if needed.
+
+### Step 3: Write HANDOFF.json
+```json
+{
+  "version": "1.0",
+  "timestamp": "{ISO8601}",
+  "phase": "{phase_number}",
+  "phase_name": "{phase_name}",
+  "task": "{current_task}",
+  "total_tasks": "{total}",
+  "status": "paused",
+  "completed_tasks": [...],
+  "remaining_tasks": [...],
+  "blockers": [...],
+  "human_actions_pending": [...],
+  "decisions": [...],
+  "uncommitted_files": [...],
+  "next_action": "{specific first action when resuming}",
+  "context_notes": "{mental state, approach}"
+}
+```
+
+### Step 4: Write .continue-here.md
+```markdown
+---
+phase: {phase}
+task: {task}
+total_tasks: {total}
+status: in_progress
+last_updated: {timestamp}
+---
+
+<current_state>
+[Where exactly are we? Immediate context]
+</current_state>
+
+<completed_work>
+- Task 1: [name] - Done
+- Task 2: [name] - In progress, [what's done]
+</completed_work>
+
+<remaining_work>
+- Task 2: [what's left]
+- Task 3: Not started
+</remaining_work>
+
+<decisions_made>
+- Decided [X] because [reason]
+</decisions_made>
+
+<blockers>
+- [Blocker]: [status/workaround]
+</blockers>
+
+<context>
+[Mental state, what were you thinking]
+</context>
+
+<next_action>
+Start with: [specific first action when resuming]
+</next_action>
+```
+
+### Step 5: Git Commit
+```bash
+git add -A
+git commit -m "wip({phase}): paused at task {task}/{total}"
+```
+
+### Step 6: Confirm
+```
+✓ Work paused successfully
+
+Current state:
+- Phase: {phase_name}
+- Task: {task} of {total}
+- Status: {status}
+- Blockers: {count}
+
+Files saved:
+- .viepilot/HANDOFF.json
+- .viepilot/phases/{phase}/.continue-here.md
+
+To resume: /vp-resume
+```
+</process>
+
+<success_criteria>
+- [ ] HANDOFF.json created with complete state
+- [ ] .continue-here.md created in phase directory
+- [ ] All sections filled with specific content
+- [ ] Uncommitted changes identified
+- [ ] Git WIP commit created
+- [ ] User knows how to resume
+</success_criteria>

package/skills/vp-request/SKILL.md

@@ -0,0 +1,250 @@
+---
+name: vp-request
+description: "Tạo request mới: feature, bug fix, enhancement, hoặc brainstorm tiếp"
+version: 0.1.0
+---
+
+<cursor_skill_adapter>
+## A. Skill Invocation
+- Skill được gọi khi user mention `vp-request`, `/vp-request`, "request", "yêu cầu", "bug", "lỗi", "feature mới", "nâng cấp"
+- Treat all user text after the skill mention as `{{VP_ARGS}}`
+
+## B. User Prompting
+Prompt user conversationally với numbered list options.
+
+## C. Tool Usage
+Use Cursor tools: `Shell`, `ReadFile`, `Glob`, `rg`, `ApplyPatch`, `WebSearch`, `WebFetch`, `Subagent`
+</cursor_skill_adapter>
+
+<objective>
+Tạo và quản lý requests cho dự án đang phát triển:
+- Bug report và fix
+- Feature request
+- Enhancement/Improvement
+- Technical debt
+- Brainstorm tiếp cho ý tưởng mới
+
+**Creates/Updates:**
+- `.viepilot/requests/{TYPE}-{NUMBER}.md`
+- `.viepilot/TRACKER.md` (thêm vào backlog)
+- `.viepilot/ROADMAP.md` (nếu approved)
+
+**Routes to:** `/vp-auto` hoặc `/vp-evolve` tùy loại request
+</objective>
+
+<execution_context>
+@$HOME/.cursor/viepilot/workflows/request.md
+</execution_context>
+
+<context>
+Optional flags:
+- `--bug` : Bug report mode
+- `--feature` : Feature request mode
+- `--enhance` : Enhancement mode
+- `--debt` : Technical debt mode
+- `--brainstorm` : Brainstorm continuation mode
+- `--list` : List pending requests
+- `--quick` : Quick mode (minimal questions)
+</context>
+
+<process>
+Execute workflow from `@$HOME/.cursor/viepilot/workflows/request.md`
+
+### Step 1: Detect Request Type
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ VIEPILOT ► REQUEST
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+What type of request?
+
+1. 🐛 Bug Report - Something is broken
+2. ✨ Feature Request - New functionality
+3. 🔧 Enhancement - Improve existing feature
+4. 🧹 Technical Debt - Code cleanup/refactor
+5. 💡 Brainstorm - Explore new ideas
+6. 📋 List Requests - View pending requests
+```
+
+### Step 2: Gather Request Details
+
+#### For Bug Report (🐛)
+```
+Bug Details:
+
+1. Title/Summary?
+2. What happened? (actual behavior)
+3. What should happen? (expected behavior)
+4. Steps to reproduce?
+5. Which part of system? (service/module)
+6. Severity? (critical/high/medium/low)
+7. Any error messages/logs?
+```
+
+#### For Feature Request (✨)
+```
+Feature Details:
+
+1. Title/Summary?
+2. What problem does it solve?
+3. Describe the feature
+4. Who benefits from this?
+5. Priority? (must-have/should-have/nice-to-have)
+6. Any specific requirements?
+
+Do you want to brainstorm this feature in detail? (y/n)
+→ If yes: route to mini brainstorm session
+```
+
+#### For Enhancement (🔧)
+```
+Enhancement Details:
+
+1. Title/Summary?
+2. Which existing feature to enhance?
+3. Current behavior
+4. Desired improvement
+5. Why is this valuable?
+6. Breaking changes? (yes/no)
+```
+
+#### For Technical Debt (🧹)
+```
+Tech Debt Details:
+
+1. Title/Summary?
+2. What needs cleanup?
+3. Current issues (performance/maintainability/etc)
+4. Proposed solution
+5. Effort estimate? (S/M/L/XL)
+6. Risk if not addressed?
+```
+
+#### For Brainstorm (💡)
+```
+Brainstorm Topic:
+
+1. What do you want to explore?
+2. Related to existing feature or completely new?
+3. Any initial ideas?
+
+→ Route to full brainstorm session with context
+```
+
+### Step 3: Create Request File
+
+Create `.viepilot/requests/{TYPE}-{NUMBER}.md`:
+
+```markdown
+# {TYPE}: {TITLE}
+
+## Meta
+- **ID**: {TYPE}-{NUMBER}
+- **Type**: Bug | Feature | Enhancement | Tech Debt
+- **Status**: new | triaged | in_progress | done | wont_fix
+- **Priority**: critical | high | medium | low
+- **Created**: {timestamp}
+- **Reporter**: User
+- **Assignee**: AI
+
+## Summary
+{SUMMARY}
+
+## Details
+{DETAILS_BASED_ON_TYPE}
+
+## Acceptance Criteria
+- [ ] {criteria_1}
+- [ ] {criteria_2}
+
+## Related
+- Phase: {if linked to phase}
+- Files: {affected files}
+- Dependencies: {related requests}
+
+## Discussion
+{Any additional context from brainstorm}
+
+## Resolution
+{Filled when resolved}
+```
+
+### Step 4: Triage & Route
+
+Based on request type and priority:
+
+**Critical Bug:**
+```
+⚠️ Critical bug detected!
+
+Options:
+1. Fix immediately (pause current work)
+2. Add to top of current phase
+3. Schedule for next available slot
+```
+
+**Feature/Enhancement:**
+```
+Request logged: {TYPE}-{NUMBER}
+
+Options:
+1. Add to current milestone backlog
+2. Brainstorm in detail first
+3. Schedule for next milestone
+4. Start working now
+```
+
+**Tech Debt:**
+```
+Tech debt logged: {TYPE}-{NUMBER}
+
+Options:
+1. Add to refactor backlog
+2. Include in next phase
+3. Create dedicated cleanup phase
+```
+
+### Step 5: Update Tracking
+
+Update `.viepilot/TRACKER.md`:
+```markdown
+## Backlog
+
+### Pending Requests
+| ID | Type | Title | Priority | Status |
+|----|------|-------|----------|--------|
+| BUG-001 | 🐛 | Login timeout | high | new |
+| FEAT-002 | ✨ | Export feature | medium | triaged |
+```
+
+### Step 6: Confirm & Next Steps
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ VIEPILOT ► REQUEST CREATED ✓
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+ ID: {TYPE}-{NUMBER}
+ Type: {TYPE}
+ Title: {TITLE}
+ Priority: {PRIORITY}
+ Status: {STATUS}
+
+ File: .viepilot/requests/{TYPE}-{NUMBER}.md
+
+ Next:
+ - /vp-request --list    View all requests
+ - /vp-auto              Start working on it
+ - /vp-request           Create another request
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+</process>
+
+<success_criteria>
+- [ ] Request type identified
+- [ ] Details gathered appropriately
+- [ ] Request file created
+- [ ] TRACKER.md updated
+- [ ] Appropriate routing suggested
+</success_criteria>

package/skills/vp-resume/SKILL.md

@@ -0,0 +1,141 @@
+---
+name: vp-resume
+description: "Resume work từ previous session với full context restoration"
+version: 0.1.0
+---
+
+<cursor_skill_adapter>
+## A. Skill Invocation
+- Skill được gọi khi user mention `vp-resume`, `/vp-resume`, "resume", "tiếp tục", "where was i"
+- Treat all user text after the skill mention as `{{VP_ARGS}}`
+
+## B. User Prompting
+Prompt user conversationally với options.
+
+## C. Tool Usage
+Use Cursor tools: `Shell`, `ReadFile`, `Glob`, `rg`, `ApplyPatch`, `WebSearch`, `WebFetch`, `Subagent`
+</cursor_skill_adapter>
+
+<objective>
+Restore complete project context và resume work seamlessly.
+
+**Reads:**
+- `.viepilot/HANDOFF.json`
+- `.viepilot/TRACKER.md`
+- `.viepilot/phases/{phase}/.continue-here.md`
+
+**After:** Context restored, ready to continue or route to appropriate action.
+</objective>
+
+<execution_context>
+@$HOME/.cursor/viepilot/workflows/resume-work.md
+</execution_context>
+
+<process>
+Execute workflow from `@$HOME/.cursor/viepilot/workflows/resume-work.md`
+
+### Step 1: Check Project Exists
+```bash
+ls .viepilot/TRACKER.md
+```
+If not exists → Error: "No ViePilot project found. Run `/vp-crystallize` first."
+
+### Step 2: Load State
+
+**Try HANDOFF.json first (preferred):**
+```bash
+cat .viepilot/HANDOFF.json
+```
+Parse: phase, task, status, next_action, context_notes
+
+**Fallback to TRACKER.md:**
+```bash
+cat .viepilot/TRACKER.md
+```
+Extract current state from Progress Overview section.
+
+**Load .continue-here.md if exists:**
+```bash
+cat .viepilot/phases/{phase}/.continue-here.md
+```
+
+### Step 3: Check Uncommitted Changes
+```bash
+git status --porcelain
+```
+If changes exist, warn user and ask how to proceed.
+
+### Step 4: Rebuild Context
+Following AI-GUIDE.md strategy:
+```yaml
+minimal_load:
+  - AI-GUIDE.md
+  - TRACKER.md
+  - PHASE-STATE.md (current phase)
+
+task_load:
+  - tasks/{current_task}.md
+  - context_required files from task
+```
+
+### Step 5: Display State Summary
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ VIEPILOT ► RESUME
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+ Project: {project_name}
+ Last Activity: {timestamp}
+
+ Current State:
+ ├── Phase: {phase_number} - {phase_name}
+ ├── Task: {task_number}/{total} - {task_name}
+ ├── Status: {status}
+ └── Progress: [████████░░] {percent}%
+
+ Context Notes:
+ {context_notes from HANDOFF.json}
+
+ Next Action:
+ {next_action from HANDOFF.json}
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+### Step 6: Offer Options
+Prompt user:
+```
+How would you like to proceed?
+
+1. Continue from task {task} (recommended)
+2. Restart current task
+3. Skip to next task
+4. View task details
+5. Run /vp-status for full overview
+6. Start /vp-auto for autonomous mode
+```
+
+### Step 7: Route to Action
+Based on user choice:
+- **Continue** → Load task context, start working
+- **Restart** → Reset task state, start fresh
+- **Skip** → Mark task skipped, move to next
+- **View** → Display task file content
+- **Status** → `Skill(skill="vp-status")`
+- **Auto** → `Skill(skill="vp-auto", args="--from {phase}")`
+
+### Step 8: Update Session
+```bash
+# Update TRACKER.md with session info
+# Clear HANDOFF.json (now active)
+```
+</process>
+
+<success_criteria>
+- [ ] HANDOFF.json or TRACKER.md loaded
+- [ ] Context rebuilt efficiently
+- [ ] State summary displayed clearly
+- [ ] User offered appropriate options
+- [ ] Routed to correct next action
+- [ ] Session continuity maintained
+</success_criteria>

package/skills/vp-rollback/SKILL.md

@@ -0,0 +1,116 @@
+---
+name: vp-rollback
+description: "Rollback to any checkpoint safely with state preservation"
+version: 0.1.0
+---
+
+<cursor_skill_adapter>
+## A. Skill Invocation
+- Skill được gọi khi user mention `vp-rollback`, `/vp-rollback`, "rollback", "quay lại"
+- Treat all user text after the skill mention as `{{VP_ARGS}}`
+
+## B. User Prompting
+Show available checkpoints and confirm before rollback.
+
+## C. Tool Usage
+Use Cursor tools: `Shell`, `ReadFile`, `Glob`, `rg`, `ApplyPatch`, `WebSearch`, `WebFetch`, `Subagent`
+</cursor_skill_adapter>
+
+<objective>
+Rollback đến bất kỳ checkpoint nào một cách an toàn, với backup và state preservation.
+
+**Checkpoints:** Git tags với prefix `vp-`
+- `vp-p{N}-t{M}` - Start of task M in phase N
+- `vp-p{N}-t{M}-done` - Task M complete
+- `vp-p{N}-complete` - Phase N complete
+
+**Safety:**
+- Backup current state before rollback
+- Validate target checkpoint exists
+- Update HANDOFF.json after rollback
+</objective>
+
+<execution_context>
+@$HOME/.cursor/viepilot/workflows/rollback.md
+</execution_context>
+
+<context>
+Optional flags:
+- `--list` : List available checkpoints
+- `--to <tag>` : Rollback to specific tag
+- `--latest` : Rollback to latest checkpoint
+- `--force` : Skip confirmation
+- `--dry-run` : Show what would happen
+</context>
+
+<process>
+
+### 1. List Checkpoints
+```bash
+git tag -l "vp-*" --sort=-creatordate
+```
+
+Display with dates and descriptions:
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ AVAILABLE CHECKPOINTS
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+ TAG                    DATE         COMMIT
+ vp-p1-complete         2026-03-30   Phase 1 done
+ vp-p1-t1-done          2026-03-30   Task 1.1 done
+ vp-p1-t1               2026-03-30   Start task 1.1
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+### 2. Validate Target
+- Check tag exists
+- Show files that will change
+- Show commits that will be undone
+
+### 3. Backup Current State
+```bash
+# Backup HANDOFF.json
+cp .viepilot/HANDOFF.json .viepilot/HANDOFF.backup.json
+
+# Create safety tag
+git tag vp-backup-{timestamp}
+```
+
+### 4. Execute Rollback
+```bash
+# Reset to checkpoint
+git reset --hard {tag}
+
+# Or soft reset (keep changes staged)
+git reset --soft {tag}
+```
+
+### 5. Update State
+Update HANDOFF.json to reflect rollback position.
+Update TRACKER.md if needed.
+
+### 6. Confirm Success
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ ROLLBACK COMPLETE ✓
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+ From: {previous_commit}
+ To:   {tag} ({commit})
+ 
+ Backup tag: vp-backup-{timestamp}
+ 
+ To undo this rollback:
+   git reset --hard vp-backup-{timestamp}
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+</process>
+
+<success_criteria>
+- [ ] Checkpoints listed with dates
+- [ ] Target validated before rollback
+- [ ] Backup created before changes
+- [ ] State files updated after rollback
+- [ ] Undo instructions provided
+</success_criteria>