BF pm-chen
Production-grade product development workflow for Chen. Triggered when the user describes a feature, product idea, or asks to build a prototype, write a PRD, define architecture, or prepare a dev handoff package. Converts natural language requirements into a structured four-stage pipeline: Business Architecture, then Interactive Prototype (HTML), then PRD (Feishu/Tencent Doc), then API Spec, then Review, then Handoff Package. The user workflow is: describe feature, AI asks clarifying questions, AI produces 4 artifacts, user reviews, deliver to dev. This skill should be used for any product design or development handoff request.
Production-grade product development workflow for Chen.
As a process F 47/100 · Will not run — References files that are not bundled: references/prd-template.md, references/api-spec-template.md, references/review-checklist.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/prd-template.md - warning
missing-refreference to a missing file: references/api-spec-template.md - warning
missing-refreference to a missing file: references/review-checklist.md - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 47/100
- 0Tools and files. 3 referenced file(s) missing: references/prd-template.md, references/api-spec-template.md, references/review-checklist.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 6 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 40Consistency. Frontmatter name (pm-chen) differs from the folder (pm-chen-workflow)
- 65Failures and branches. 3 branches
- 85Steps. 78 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 2082 tokens
- low 11 top-level sections: this looks like several domains in one skill
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
- +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
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +3Description length 635: enough signal without eating the budget
- +4Structure: 33 headings
- +3Step-by-step instructions: 78 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.