gsd-review-checklist

Automate final review of architecture, contracts, frontend behavior, build wiring, packaging, and verification.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/Sheon-S/ignition-sdk-agent-kit --skill gsd-review-checklist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-review-checklist
Source: https://github.com/Sheon-S/ignition-sdk-agent-kit/tree/main/.agents/skills/gsd-review-checklist
Command: npx skills add https://github.com/Sheon-S/ignition-sdk-agent-kit --skill gsd-review-checklist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Final review checklist that ensures architecture, contracts, embedded frontend behavior, build wiring, packaging, and verification are complete before declaring non-trivial changes finished.

Core Features & Use Cases

  • Consolidates architecture, integration, and packaging checks into a single, repeatable process.
  • Helps teams verify runtime handoffs, documentation parity, and release readiness across modules.
  • Use Case: before finishing a feature that touches multiple subsystems, run this checklist to confirm all criteria are met.

Quick Start

Run the GSD Review Checklist before declaring any non-trivial task complete to ensure architecture, integration, and packaging alignment.

Frequently Asked Questions about gsd-review-checklist

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

FAQPage Schema
How do I verify architecture and packaging alignment before finishing a feature?

A final review checklist automates the verification of architecture, contracts, embedded frontend behavior, build wiring, and packaging to ensure non-trivial changes are fully complete before handoff.

What is a final review checklist for cross-cutting subsystem changes?

A final review checklist is a repeatable process that consolidates architecture, integration, and packaging checks to verify completion criteria, handoff readiness, and documentation parity across multiple subsystems.

When do I need to run a release readiness checklist for multiple modules?

Run a release readiness checklist before finishing any non-trivial task that touches multiple subsystems, hooks, and runtime handoffs to confirm all completion criteria and documentation requirements are met.

How do I check runtime handoffs and documentation parity across modules?

Run a consolidated review checklist to check runtime handoffs, documentation parity, and release readiness across modules, verifying that all integration and architecture criteria are satisfied.

Does this review checklist work for features touching multiple subsystems and hooks?

Yes, this checklist specifically applies to cross-cutting changes that touch multiple subsystems, hooks, and runtime handoffs, verifying all architecture and packaging criteria before marking the task complete.