SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillslcs-prd-reviewer

lcs-prd-reviewer

Security & auditing

View repository

Updated 10-16 00:22

About this skill

LCS PRD Reviewer Skill

Shared Coding Contract

  • Refer to Shared Coding Workflow Contract in ../lcs-shared/contract.md for folder conventions, Handoff format, and token optimization.

Purpose

  • Review prd.md, harden acceptance criteria, test strategy, security, performance, and maintainability.
  • Write and save the hardened PRD into prd-enhanced.md inside the same work-item directory.

Trigger

  • Activate when user requests to "review prd", "audit prd", "harden prd", "security review of prd", or when completing the PRD generation phase.

OKF Frontmatter & Writing Safety

  • When creating prd-enhanced.md, include YAML frontmatter following the schema in ../lcs-shared/contract.md.
  • Follow the Artifact Writing Safety rules in contract.md — generate content first, write one file, verify, stop on failure.

Trigger

Activate when user requests related to this skill's purpose. See description field in YAML frontmatter for trigger phrases.

Behavior checklist

  • Read .lcs/state.md to identify the active work-item directory: .lcs/work-items/{timestamp}-{slug-work-item}/.
  • Read prd.md inside that active directory.
  • If intent.md exists in that directory, read it and check prd.md for material drift against its Problem, Proposed Outcome, Constraints, and Out of Scope. Flag any conflict under a ## Intent Alignment note before hardening further.
  • Review it for gaps: ambiguous acceptance criteria, missing tests, security, performance, and missing Affected Areas / Files.
  • Create or update prd-enhanced.md in the same directory with the fully hardened specifications.
  • Keep the original prd.md intact, but write all improvements and hardenings directly to prd-enhanced.md.
  • Add ## Preservation Check. Prove every SRC-### from prd.md still exists in prd-enhanced.md. If a requirement is removed, list it under ## Intentionally Removed with reason. If a requirement was silently dropped, restore it before finishing.
  • Update Review Notes section in prd-enhanced.md with:
    • Last Reviewed: {timestamp}
    • Summary: <summary of revisions/gaps found>
    • Changes Applied:
  • End with Handoff section pointing to the next logical step (e.g., lcs-tosrs for SRS transformation), including Source of Truth Bundle, Must Preserve IDs, and Unresolved IDs.

State Synchronization

After successful prd-enhanced.md creation, update .lcs/state.md:

  • current_phase: prd_review
  • work_items[state.current_work].phase = prd_review
  • work_items[state.current_work].updated_at = <current-ISO-timestamp>
  • timestamp: <current-ISO-timestamp>
  • last_session_note: Hardened prd.md into prd-enhanced.md for <work-name>

Prompt templates

  • Starter: "Review prd.md dan perbaiki menjadi prd-enhanced.md agar siap di-slice"
  • Checklist ask: "Apakah acceptance criteria cukup spesifik?"

prd-enhanced.md Structure Must be exact structure as prd.md:

PRD:

Objective

Background

<why we are doing this, context>

Source Context

<links to explore.md, intent.md, debug.md, or other sources>

Scope

Non-Goals

Requirements

Technical Approach

<architecture, libraries, database changes, APIs>

Affected Areas / Files

Security Considerations

<vulnerabilities, authentication, authz>

Performance Considerations

<latency, database query limits, caching>

Potential Bugs / Edge Cases

<what could go wrong, validations>

Acceptance Criteria

  • AC 1:
  • AC 2:

Intent Alignment

<if intent.md is present: confirm Problem, Proposed Outcome, Constraints, and Out of Scope remain respected. Flag any material drift here rather than silently accepting it.>

Preservation Check

SRC ID Status Notes
SRC-001 preserved <where/how it appears in enhanced PRD>
SRC-002 enhanced

Intentionally Removed

Only list requirements removed after explicit scope decision or contradiction resolution.

SRC ID Reason
<SRC-### or None>

Test Strategy

  • Unit:
  • Integration:
  • E2E:

Review Notes

  • Last Reviewed:
  • Summary:
  • Changes Applied:

Chain of Truth Report

Level

Strict

Sources Checked

  • .lcs/state.md
  • .lcs/work-items/{timestamp}-{slug-work-item}/prd.md lines {range}

Assumptions

  • <label each [verified] or [unverified]>

Plan

Actions Taken

Verification

<Automated checks attempted; document every failure>

Report

<Explicit pass/fail per acceptance criterion>

Handoff

Next recommended skill: lcs-tosrs Next file to read: .lcs/work-items/{timestamp}-{slug-work-item}/prd-enhanced.md Current phase: prd_review Current confidence: high Blocking questions: None Risks to carry forward: Source of Truth Bundle: .lcs/state.md, prd.md, prd-enhanced.md, intent.md if present Must Preserve IDs: SRC-001, SRC-002, ... Unresolved IDs: Suggested next command: Transform prd-enhanced.md menjadi SRS deterministik (lcs-tosrs)

Chain of Truth Level

Level: Strict

This skill follows the LCS Chain of Truth protocol at the declared level.