CtrlK
BlogDocsLog inGet started
Tessl Logo

prp-prd-update

Maintains PRD implementation-phase status and artifact links. Always use when a PRP workflow records a planned, implemented, or merged phase in its source PRD, when the user asks to update PRD progress, or when the user invokes $prp-prd-update.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

93%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, well-structured instruction skill that gives concrete per-stage rules and explicit verification steps with strong idempotency guardrails. The only minor gap is that the post-edit re-read verification does not spell out the recovery loop when the re-read mismatches.

Suggestions

Add an explicit error-recovery step in 'Verify and report' (e.g. 'If the re-read does not match the requested stage, fix the row and re-verify before returning') to lift workflow_clarity to 5.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding; it never explains what a PRD/PRP is and every line (guardrails, stage rules, verification) earns its place.

5 / 5

Actionability

Concrete, executable guidance per stage (require file existence, record absolute paths in named columns, verify the PR via GitHub, set Status to specific values); absence of code is appropriate for an instruction-only skill.

5 / 5

Workflow Clarity

Clear Resolve -> Apply -> Verify sequence with explicit validation checkpoints ('Stop if the phase is missing, duplicated...', 'Re-read the exact phase row after editing'), but the error-recovery path after a failed re-read is only implied rather than stated.

4 / 5

Progressive Disclosure

Under 50 lines, single-purpose, no external references needed, with three well-organized sections that keep navigation trivial.

5 / 5

Total

19

/

20

Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states its purpose and provides explicit, natural trigger conditions with a distinct invocation token. Specificity of capabilities is the only soft spot, since it summarizes the action rather than enumerating the concrete stage operations.

Suggestions

Optionally enumerate the concrete per-stage actions (record plan path, record report path and PR URL, set status) to lift specificity from 3 to 4-5.

Add a couple more natural user phrasings (e.g. 'mark PRD phase as done', 'link the PR to a phase') to round out trigger-term coverage.

DimensionReasoningScore

Specificity

Names the PRD domain and concrete actions ('Maintains PRD implementation-phase status and artifact links'), but only 1-2 actions are listed rather than a comprehensive set.

3 / 5

Completeness

Explicitly answers both what ('Maintains PRD implementation-phase status and artifact links') and when ('Always use when...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural trigger coverage ('update PRD progress', 'PRP workflow records a planned, implemented, or merged phase', '$prp-prd-update'), though a few common phrasings are missing.

4 / 5

Distinctiveness Conflict Risk

Clear PRP/PRD-phase niche with a distinct invocation token ($prp-prd-update) and specific phase-status triggers, giving minimal conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Wirasm/prp
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.