AC sdlc-assistant
A guided assistant for software development teams across roles including developers, testers (QA), product owners (PO), project managers (PM), and business analysts (BA). Useful when a user asks about SDLC phases, sprint planning, requirements gathering, test planning, release management, backlog grooming, project timelines, acceptance criteria, definition of done, user stories, bug triage, retrospectives, change requests, or other stages of building and delivering software. Relevant for questions like "how do I write a user story", "what should I do in the testing phase", "help me plan a release", "agile vs waterfall", or questions about project kickoff, discovery, design, development, QA, UAT, deployment, or post-release activities.
As a process C 62/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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: 4. 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 62/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 55Failures and branches. 1 branches
- 100Tools and files. No external tools needed
- 100Steps. 32 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1317 tokens
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
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 744: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 32 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 93.