AA vibe-coding-workflow
Structured 5-phase AI-assisted development workflow (requirements → architecture → code generation → debugging → iteration). Use when the user mentions "vibe coding", wants a structured multi-phase AI collaboration for a software project, says "help me build a project step by step", asks how to start a new feature or project with AI, encounters bugs they can't resolve, wants to refactor messy code, or asks about AI-assisted development workflows. Also use when the user says "Phase 1/2/3/4/5", "requirements doc", "architecture design", or explicitly asks to "follow the workflow".
As a process A 81/100 · Runs to the end — weak spots: result and completion, running it twice
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 81/100
- 30Running it twice. 2 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 55Failures and branches. 1 branches
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 62 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1802 tokens
- 100Progress reporting. Reports progress
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 585: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 62 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.