Borrowing it
Nothing to install: this file belongs to xiaolai/vmark. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/xiaolai/vmark/main/.claude/commands/feature-workflow.mdgit clone --depth 1 https://github.com/xiaolai/vmarkWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/xiaolai/vmark/feature-workflow)<a href="https://agentmods.dev/commands/xiaolai/vmark/feature-workflow"><img src="https://agentmods.dev/badge/commands/xiaolai/vmark/feature-workflow/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/xiaolai/vmark/feature-workflow"><img src="https://agentmods.dev/badge/commands/xiaolai/vmark/feature-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00011 | $0.00596 |
| Opus 5.5 | $0.00004 | $0.00238 |
| Sonnet 5.5 | $0.00002 | $0.00119 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
feature-workflow scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Workflow (Gated Orchestrator)
Goal: take a high-level plan and drive it to completion using specialized subagents, TDD gates, and explicit acceptance.
Inputs
work-name: short slug (e.g.file-mgmt-rebuild-phase0)- Optional: an existing plan doc to refine.
Workflow (always in this order)
-
Plan (Planner agent)
- Create or refine a modular plan in the project docs directory.
- Break into Work Items with explicit acceptance criteria, tests, and rollback notes.
-
Spec Check (Spec Guardian agent)
- Validate plan vs specs and project rules in
AGENTS.mdand.claude/rules/*.md. - Stop if specs conflict or constraints are violated.
- Validate plan vs specs and project rules in
-
Impact (Impact Analyst agent)
- For each Work Item, map the minimal file set, dependency edges, and risks.
- Propose the smallest correct change boundaries.
-
Implement (Implementer agent)
- For each Work Item, do a preflight investigation before writing tests:
- Reproduce/describe current behavior and expected behavior.
- Trace the exact call chain and identify the smallest test seam.
- Confirm the minimal file impact; update the Impact map if needed.
- Subagent delegation is encouraged for this "map and report" step.
- For each Work Item: write the test first (RED), implement (GREEN), refactor safely.
- Encourage subagent delegation for large/mechanical diffs; always review + run gates after.
- Keep side effects isolated; keep changes local; keep files under ~300 lines.
- For each Work Item, do a preflight investigation before writing tests:
-
Test (Test Runner agent)
- Run
pnpm check:all(andcargo testwhen Rust changes). - If UI flows are impacted, request the user to run the app and use Tauri MCP for E2E.
- Run
-
Audit (Auditor agent)
- Review diffs for correctness, architecture drift, and rule violations.
- If issues found: loop back to Implement for fixes.
-
Manual Test Guide (Manual Test Author agent)
- Update manual testing docs incrementally per Work Item.
- Ensure final “end-to-end” guide exists and is coherent.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 62 lines · 11 tokens per session scan A f71621e59642
feature-workflow is a command published in the GitHub repository xiaolai/vmark (878 stars, last pushed yesterday), licensed ISC. It adds 11 tokens to every session and 596 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.