gnd-critique

Critique executed plans against project context and governing READMEs.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/ironloon/peninsular-reveries --skill gnd-critique
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gnd-critique
Source: https://github.com/ironloon/peninsular-reveries/tree/main/.pi/skills/gnd-critique
Command: npx skills add https://github.com/ironloon/peninsular-reveries --skill gnd-critique

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evaluate delivered work against the plan and its governing context to ensure alignment between intent and outcome, guiding corrective actions and quality improvements.

Core Features & Use Cases

  • Plan critique: Evaluate an implemented live plan after navigation, validating that shipped work matches the intended goals.
  • Field review: Triage runtime or workflow observations, document findings, and archive actionable corrections.
  • Process governance: Append critique findings to plans, update process files, and inform backlog for continuous improvement.

Quick Start

Execute a critique by reviewing the latest plan implementation against the project context and delivering a structured findings report.

Frequently Asked Questions about gnd-critique

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I critique gaps between a delivered project and its original plan?

To critique gaps between a delivered project and its plan, you evaluate the shipped work against project context and governing READMEs, documenting evidence and impact to drive corrective actions.

What is the best way to document runtime observations during a workflow analysis?

Documenting runtime observations during a workflow analysis involves triaging field review findings, archiving actionable corrections, and appending them to process files to inform backlog improvements.

How do I perform a plan review after project delivery?

Performing a plan review after delivery requires validating the implemented live plan against intended goals, identifying execution gaps, and returning structured findings with actionable corrections.

Can I use project management documentation to ensure quality assurance after implementation?

Yes, you can validate deliverables against project documentation and governing READMEs to ensure quality assurance, capturing deviations and generating artifacts for process governance updates.

When should I not use a plan critique for project management?

Avoid using plan critique when a project lacks an original plan, governing context, or deliverables, as validation requires existing documentation to identify execution gaps and inform corrective action.