postrodeo

Audit post-build artifacts against specifications and coding standards.

Updated May 10, 2026
One-click install
npx skills add https://github.com/michaeljboscia/goatrodeo --skill postrodeo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: postrodeo
Source: https://github.com/michaeljboscia/goatrodeo/tree/main/ceremonies/postrodeo
Command: npx skills add https://github.com/michaeljboscia/goatrodeo --skill postrodeo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the post-build review process to ensure the implemented features match the specifications and adhere to coding standards, saving time and reducing errors.

Core Features & Use Cases

  • Build Retrospective: Audits the built product against the spec, checking for deviations and analyzing issues.
  • Semantic Logic Check: Reviews the code for logical errors and adherence to the spec, beyond just passing tests.
  • Audit Effectiveness: Evaluates the effectiveness of audits throughout the development process.
  • Documentation Reconciliation: Ensures the final documentation accurately reflects the built product.

Quick Start

Run the postrodeo skill after the build to automate the review process and generate a comprehensive report.

Frequently Asked Questions about postrodeo

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

FAQPage Schema
How do I automate post-build reviews to ensure spec integrity?

Automate post-build reviews by auditing build artifacts against the implementation plan and version control history to identify spec deviations. This process evaluates code quality, checks for logical errors, and generates a comprehensive retrospective report.

What is a build retrospective and how does it check code quality?

A build retrospective audits the built product against specifications to analyze deviations and issues. It reviews code for logical errors and semantic adherence to the spec, ensuring features meet coding standards beyond just passing tests.

How do I reconcile documentation with actual build artifacts after development?

Reconcile documentation by cross-referencing final docs with the built product and version control history. This ensures the documentation accurately reflects the implemented features and coding standards verified during the post-build analysis.

Do I need version control history to perform a post-build analysis?

Yes, post-build analysis requires access to build artifacts, the implementation plan, and version control history. These inputs allow the review process to accurately audit the build against the spec and evaluate audit effectiveness.

Can a build retrospective check for semantic logic errors instead of just running tests?

Yes, the build retrospective performs semantic logic checks to review code for logical errors and spec adherence. It evaluates the implementation beyond standard test execution to ensure the build meets specifications and coding standards.

What is the best way to evaluate audit effectiveness during software development?

Evaluate audit effectiveness by running an automated post-build review that analyzes deviations and issues throughout the development process. This generates a comprehensive report assessing how well the build adheres to the implementation plan and coding standards.