Feature Workflow
Run the binding 6-gate feature workflow end-to-end per rule 47 (Plan → Independent Plan Audit → TDD Implementation → Implementation Audit Loop → Device/Integration Verification → Merge). Use this skill whenever the user wants to implement a new feature in vreader, asks 'implement feature #N', 'work on feature 47', 'start the feature workflow', 'plan + build feature X', or describes building a new capability that doesn't yet exist. NOT for fixing broken implementations (that's fix-issue). The skill drives the row from `TODO` → `VERIFIED` through six gates that must never be skipped — author/aud
Install
npx skills add lllyys/vreader --skill feature-workflowgit clone --depth 1 https://github.com/lllyys/vreader.git /tmp/vreader
mkdir -p ~/.claude/skills
cp -r /tmp/vreader/.claude/skills/feature-workflow ~/.claude/skills/feature-workflowPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Feature Workflow (rule 47, six gates, never skip one) Drives a feature from `TODO` → `VERIFIED` through the binding 6-gate sequence in `.claude/rules/47-feature-workflow.md`: > Plan → Independent Plan Audit → TDD Implementation → Implementation > Audit Loop → Device/Integration Verification → Merge → (close gate) Each gate has an explicit **required artifact**, **author/auditor separation rule**, **tracker status transition**, **blocking hook**, and **exit criteria**. You don't enter the next gate until the current gate's exit criteria are met. Multiple iterations within a gate are normal. ## Input ```text $ARGUMENTS ``` `$ARGUMENTS` is the feature identifier — either a numeric id from `docs/features.md` (e.g. `48`) or a short slug (e.g. `materializing-restore`). If empty, list `TODO`/`PLANNED` candidates from `docs/features.md` and ask the user to pick. ## Scope guard — read this first This skill is for **features only** (capabilities never implemented). If the work is fixing a broken implementation, stop here and use `/fix-issue`. The bug-vs-feature distinction is binding per AGENTS.md; running a fix through this skill skips the bug-tracker workflow. ## Hooks you'll trip | Hook | Triggers when | What it requires | |---|---|---| | `check_gh_issue_mirror.sh` | `Edit/Write/MultiEdit` on `docs/features.md` | mirror-required rows (`PLANNED`/`IN PROGRESS`/`DONE`/`VERIFIED`) must have `GH: #N` in Notes column |
Details
- Skill name
feature-workflow- Repository
- lllyys/vreader
- Path
.claude/skills/feature-workflow/SKILL.md- Repo updated
- 6 August 2026
FAQ
What does the Feature Workflow skill do?
Run the binding 6-gate feature workflow end-to-end per rule 47 (Plan → Independent Plan Audit → TDD Implementation → Implementation Audit Loop → Device/Integration Verification → Merge). Use this skill whenever the user wants to implement a new feature in vreader, asks 'implement feature #N', 'work on feature 47', 'start the feature workflow', 'plan + build feature X', or describes building a new capability that doesn't yet exist. NOT for fixing broken implementations (that's fix-issue). The skill drives the row from `TODO` → `VERIFIED` through six gates that must never be skipped — author/aud
How do I install the Feature Workflow skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add lllyys/vreader --skill feature-workflow. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Feature Workflow popular?
It lives in lllyys/vreader, which has 49 GitHub stars and 21 forks.
Related skills
AI Coding Agents
49lllyys/vreader
Comprehensive guide for using Codex CLI (OpenAI) and Claude Code CLI (Anthropic) - AI-powered coding agents. Use when orchestrating CLI commands, automating tasks, configuring agents, or troubleshooting issues.
Dispatch
49lllyys/vreader
Parallel lane dispatch — the ONLY sanctioned multi-item fan-out (feature #130, rule 55). Use when the user asks to fix several bugs at once ('fix #a #b #c'), implement independent feature WIs in parallel, or run a dispatch batch. Orchestrates worktree-isolated implementer lanes on leased simulators, validates HANDOFFs, and runs the serial integration tail (rebase → re-test → tracker/docs → version-at-slot → PR → merge-from-worktree → tag). A single item degrades to the inline /fix-issue or /feature-workflow flow.
File Bug
49lllyys/vreader
Create a GitHub issue for a bug row in docs/bugs.md and stamp `GH: #N` into its Notes column. Use this skill whenever the user wants to file/mirror/create a GH issue for an existing bug row, or asks 'create issue for bug #N', 'file bug 115', 'mirror bug 42 to GH', 'this bug needs a GH issue'. Also trigger when the `check_gh_issue_mirror.sh` PreToolUse hook blocks an edit to a `docs/bugs.md` row because it lacks `GH: #N`. Stays strictly in the mirror-an-existing-row scope — do not use for triaging new bugs (that's the triage skill) or fixing bugs (that's fix-issue).
File Feature
49lllyys/vreader
Create a GitHub issue for a feature row in docs/features.md and stamp `GH: #N` into its Notes column. Use this skill whenever the user wants to file/mirror/create a GH issue for an existing feature row, or asks 'create issue for feature #N', 'file feature 47', 'mirror feature 32 to GH', 'this feature needs a GH issue'. Also trigger when the `check_gh_issue_mirror.sh` PreToolUse hook blocks an edit to a `docs/features.md` row because it lacks `GH: #N`. Skip if status is `TODO` (promote to `PLANNED` first) or Notes contains `Mirror: no`.
Fear
113Hmbown/Wizards-of-the-Ghosts
Fear makes targets run from danger. The real-world version is structured pessimism: pre-mortem analysis, worst-case scenario generation, and risk amplification exercises that counteract the natural optimism bias in planning. Fear is the antidote to "it'll probably be fine.
Freedom of Movement
113Hmbown/Wizards-of-the-Ghosts
Freedom of Movement is for processes that should be moving but are caught in glue: locked files, blocked ports, circular dependencies, wedged jobs, or permissions that almost work. The skill is about diagnosing the restraint, then removing or routing around it without tearing the whole system apart. It favors unblocking over brute force.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.