AC fde-prd-writer
Stage 3 of FDE Delivery Loop. Turn an approved problem-discovery package and POC engagement charter into an English POC PRD specification handoff for engineering, QA, deployment, Agent Skill design, and POC execution. Use to write, improve, or review POC PRDs, functional requirements, acceptance criteria, test scenarios, scope decisions, and downstream handoffs. Do not use for initial discovery, customer commitments, prototype construction, or production operations.
Stage 3 of FDE Delivery Loop.
As a process C 61/100 · Has gaps — weak spots: inputs and preconditions, failures and branches, 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: 13. 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 61/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 100Steps. 10 steps
- 100Result and completion. Output format and completion criterion are stated
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 772 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
- +5Description has no quoted example phrases that should trigger the skill
- +4No input/output examples
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 470: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 10 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (6 of 6)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 95.