Agent skill
vrau
Use when starting or resuming a vrau workflow - routes to correct phase
Stars
163
Forks
31
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/development/vrau
SKILL.md
Vrau Workflow
⚠️ CRITICAL SAFETY RULE ⚠️
NEVER COMMIT TO MAIN BRANCH
Before doing ANYTHING, check current branch:
bash
git branch --show-current
If on main/master:
- STOP immediately
- Create a new branch OR use worktree
- NEVER proceed with commits on main
This is non-negotiable. No exceptions. Ever.
On Start
- Scan
docs/designs/for folders matchingYYYY-MM-DD-* - If none: start new workflow (see below)
- If one: auto-select, detect state, ask about worktree/branch (see Resuming Workflow below), invoke correct phase
- If multiple: ask user which to resume (or start new, or delete old), then ask about worktree/branch (see Resuming Workflow below), invoke correct phase
New Workflow Setup
- Ask user for task description
- Ask: Start from GitHub issue?
- Yes → get issue number, set Doc Approach B
- No → set Doc Approach A
- (Optional) Ask: Local-only mode? → set Doc Approach C, create .no-commit.local
- Ask: Worktree or new branch?
- Worktree → use superpowers:using-git-worktrees
- New branch →
git checkout -b <workflow-name>andgit push -u origin <workflow-name>
- Update main first:
git checkout main && git pull - Create worktree OR branch based on choice
- Create folder
docs/designs/YYYY-MM-DD-<slug>/ - Create README.md with Doc Approach and issue number (if any)
- Create execution-log.md (see format below)
- Commit, push (skip if Doc Approach C)
- Invoke vrau:brainstorm
Resuming Workflow
When resuming an existing workflow:
- Update main first:
git checkout main && git pull - Ask: Worktree or new branch?
- Worktree → use superpowers:using-git-worktrees
- New branch →
git checkout -b <workflow-name>-<phase>andgit push -u origin <workflow-name>-<phase>
- Create worktree OR branch based on choice
- Proceed to invoke correct phase
Why: User must choose worktree/branch preference every time they resume work. Never assume.
State Detection
Read docs/designs/<workflow>/execution-log.md:
- Phase: brainstorm | plan | execute
- Status of current phase
Fallback if no execution log - check files:
- Only README.md → brainstorm
- Has design/.md, no plan/.md → plan
- Has plan/*.md → execute
- If unclear → ASK USER
Execution Log Format
# Execution Log: <workflow>
## Workflow Context
- **Task:** <description>
- **Phase:** brainstorm | plan | execute
- **Branch:** <branch name>
- **Issue:** #<number> or (none)
## Status
- **Current Step:** <step number and name>
- **Last Updated:** <timestamp>
Routing
- Brainstorm needed → invoke vrau:brainstorm
- Plan needed → invoke vrau:plan
- Execute needed → invoke vrau:execute
Didn't find tool you were looking for?