ln-312-review-findings-worker
Use when an evaluation coordinator needs normalized findings from target artifacts and research evidence.
- License 许可
- MIT
- 最近更新
- 2026-06-15
- Stars
- ★ 2
- Forks
- 1
01 前言 Front Matter
- name
- ln-312-review-findings-worker
- license
- MIT
- description
- Use when an evaluation coordinator needs normalized findings from target artifacts and research evidence.
02 资源文件 9
- 参考文档references/cross_reference_validation.md4.1 KB
- 参考文档references/epistemic_protocol.md3.4 KB
- 参考文档references/evaluation_summary_contract.md1.8 KB
- 参考文档references/evaluation_worker_runtime_contract.md2.0 KB
- 参考文档references/penalty_points.md4.2 KB
- 参考文档references/phase2_research_audit.md12.2 KB
- 参考文档references/plan_review_pipeline.md2.4 KB
- 参考文档references/premortem_validation.md6.3 KB
- 参考文档references/research_methodology.md5.4 KB
03 SKILL.md 正文
Paths: File paths (
references/,../ln-*) are relative to this skill directory.
Type: L3 Worker Category: 3XX Planning
Review Findings Worker
Mandatory Read
MANDATORY READ: Load references/evaluation_worker_runtime_contract.md, references/evaluation_summary_contract.md
MANDATORY READ: Load ../ln-310-multi-agent-validator/references/phase2_research_audit.md, ../ln-310-multi-agent-validator/references/penalty_points.md
MANDATORY READ: Load ../ln-310-multi-agent-validator/references/premortem_validation.md, ../ln-310-multi-agent-validator/references/cross_reference_validation.md
Purpose
- analyze the target artifact or diff
- convert evidence into normalized findings
- for
mode=story: calculate penalty points across 30 criteria perphase2_research_audit.md - for
mode=plan_review: evaluate criteria #5, #6, #21, #28 only (no penalty accumulation) - avoid narrative-only review output
Mode Gate
mode=story: full pipeline — pre-mortem, cross-reference, penalty points across 30 criteria, build fix planmode=plan_review: applicability check, stack detection, evaluate criteria #5 (standards), #6 (library versions), #21 (alternatives), #28 (library features) only, normalize findings without penalty accumulation
Runtime
Runtime family:
evaluation-worker-runtime
Required manifest fields:
identifierphase_ordersummary_kind=review-findingsoperation=findings
Recommended phase_order:
PHASE_0_CONFIGPHASE_1_LOAD_TARGETPHASE_2_PREMORTEM(mode=story, complexity >= Medium)PHASE_3_CROSS_REFERENCE(mode=story, multi-story Epic)PHASE_4_CRITERIA_AUDITPHASE_5_PENALTY_CALCULATION(mode=story only)PHASE_6_NORMALIZE_FINDINGSPHASE_7_WRITE_SUMMARYPHASE_8_SELF_CHECK
Workflow
Phase 0: Config
Load runtime manifest, target identifiers, and any linked research artifact paths.
Phase 1: Load Target
Load only the target artifacts needed for the review scope.
Phase 2: Pre-mortem (mode=story)
Execute pre-mortem analysis per premortem_validation.md:
- Skip for trivial Stories (1-2 tasks, no external deps, known tech).
- Execute for Stories with complexity >= Medium (3+ tasks, external deps, or unfamiliar tech).
- Tigers (evidence-based risks) feed Risk criterion #20 — add to risk table BEFORE penalty calc.
- Elephants (unstated assumptions) feed Assumptions criterion #24 — add with
[pre-mortem]tag, Confidence=LOW. - Paper Tigers (fears without evidence) — document and dismiss.
- Include pre-mortem table in audit report.
Phase 3: Cross-Reference (mode=story)
Execute cross-reference analysis per cross_reference_validation.md:
- Skip if Epic has only 1 Story or all siblings Done/Canceled.
- Load sibling Stories via
list_issues(project=Epic.id). - Check AC overlap (#25): structured traceability first, keyword fallback advisory-only.
- Check task duplication (#26): structured match primary.
- Include cross-reference findings in audit report.
Phase 4: Criteria Audit
mode=story: evaluate all 30 criteria against Story/Tasks perphase2_research_audit.mdAuto-Fix Actions Reference.mode=plan_review: evaluate criteria #5, #6, #21, #28 only (standards + solution groups).- Cross-check claims against provided research evidence when present.
Phase 5: Penalty Calculation (mode=story)
- Assign penalty points per violation using severity levels from
phase2_research_audit.md(CRITICAL=10, HIGH=5, MEDIUM=3, LOW=1). - Apply multiple-violation rules per
penalty_points.mdCalculation Rules. - Calculate total penalty points.
- Build fix plan for each violation.
- Format penalty audit table per
penalty_points.mdReport Format.
Phase 6: Normalize Findings
Each finding should prefer structured fields such as:
idseveritycategorysubjectevidencerecommendation
Phase 7: Write Summary
Emit summary_kind=review-findings.
Payload must include:
worker=ln-312statusoperation=findingswarnings
Prefer these fields when available:
findingsmetrics.penalty_total(mode=story)metrics.criteria_violated(list of criterion numbers)metrics.fix_plan(array of {criterion, action, severity})metrics.premortem_summary(when executed)metrics.cross_reference_summary(when executed)
Phase 8: Self-Check
- Remove duplicates.
- Remove unsupported claims.
- Verify penalty calculation matches
penalty_points.mdrules (mode=story). - Record
pass=trueonly after summary write.
Definition of Done
- [ ] Target artifact loaded
- [ ] Pre-mortem executed or justified as skipped (mode=story)
- [ ] Cross-reference executed or justified as skipped (mode=story)
- [ ] Criteria audit completed (30 for story, #5/#6/#21/#28 for others)
- [ ] Penalty points calculated and fix plan built (mode=story)
- [ ] Findings normalized
- [ ] Unsupported claims removed
- [ ]
review-findingssummary written - [ ] Self-check passed
Version: 1.0.0 Last Updated: 2026-04-10
04 同仓库更多 Skills
solana-dev
Use when user asks to "build a Solana dapp", "write an Anchor program", "create a token", "debug Solana errors", "set up wallet connection", "test my Solana program", "deploy to devnet", or "explain Solana concepts" (rent, accounts, PDAs, CPIs, etc.). End-to-end Solana development playbook covering wallet connection, Anchor/Pinocchio programs, Codama client generation, LiteSVM/Mollusk/Surfpool testing, and security checklists. Integrates with the Solana MCP server for live documentation search. Prefers framework-kit (@solana/client + @solana/react-hooks) for UI, wallet-standard-first connection (incl. ConnectorKit), @solana/kit for client/RPC code, and @solana/web3-compat for legacy boundaries.
generating-trading-signals
Generate trading signals using technical indicators (RSI, MACD, Bollinger Bands, etc.). Combines multiple indicators into composite signals with confidence scores. Use when analyzing assets for trading opportunities or checking technical indicators. Trigger with phrases like "get trading signals", "check indicators", "analyze for entry", "scan for opportunities", "generate buy/sell signals", or "technical analysis".
prediction-monitor
Prediction Monitor - Auto-activating skill for ML Deployment. Triggers on: prediction monitor, prediction monitor Part of the ML Deployment skill category.
strategy-advisor
High-level strategic thinking and business decision guidance for planning and direction-setting. Use when: making strategic decisions, evaluating business options, setting direction, analyzing trade-offs, or when user mentions strategy, business planning, competitive analysis, or long-term planning.
app-paywall-pilot
Design, audit, debug, and implement App Store-compliant mobile paywalls, subscription flows, pricing screens, trials, offers, feature gates, and subscription lifecycle UX. Use when the user asks to audit my paywall, fix App Store 3.1.2 rejection, improve trial-to-paid, choose plans/prices/trials, review RevenueCat/Adapty/Apphud/Superwall setup, calculate LTV/ROAS, or build paywall implementation.
figma
Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.