reviewing-tribal-plan

Validate implementation plans against tickets, architectural invariants, and design documentation.

9|Updated Feb 11, 2026

Search Tags:#code review #software design #implementation plan #architectural review #plan validation #ticket compliance

Ready to run

npx skills add https://github.com/samfolo/tribal --skill reviewing-tribal-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reviewing-tribal-plan
Source: https://github.com/samfolo/tribal/tree/main/.claude/skills/reviewing-tribal-plan
Command: npx skills add https://github.com/samfolo/tribal --skill reviewing-tribal-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill rigorously reviews implementation plans before coding begins, ensuring architectural soundness, adherence to requirements, and compliance with design documents, thereby preventing costly post-implementation fixes.

Core Features & Use Cases

Plan Validation: Assesses plans against tickets, milestone documents, RFCs, and codebase realities.
Discrepancy Identification: Flags issues related to acceptance criteria coverage, scope adherence, invariant compliance, and architectural soundness.
Use Case: Before a new feature is coded, this Skill acts as an adversarial reviewer to catch potential architectural flaws or missed requirements in the proposed implementation plan.

Quick Start

Use the reviewing-tribal-plan skill to review the plan located at '/path/to/implementation/plan.md' for ticket number 123.

Frequently Asked Questions about reviewing-tribal-plan

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

FAQPage Schema

How do I validate an implementation plan against project tickets and design documents?▼

To validate an implementation plan, you review it against project tickets, architectural invariants, and milestone documents to identify deviations, scope creep, and potential architectural fragility before development commences.

What is architectural review for software implementation plans?▼

Architectural review for implementation plans is the process of assessing proposed software designs against acceptance criteria and codebase realities to ensure architectural soundness and compliance with source-of-truth hierarchy before coding begins.

How do I check an implementation plan for scope creep and missed requirements?▼

Checking an implementation plan for scope creep involves flagging discrepancies related to acceptance criteria coverage, scope adherence, and invariant compliance to catch missed requirements before development starts.

Can I use an adversarial review to catch architectural flaws in a proposed plan?▼

Yes, you can use an adversarial review to rigorously assess implementation plans against RFCs and codebase realities, catching potential architectural flaws and preventing costly post-implementation fixes.

When do I need to review an implementation plan before coding begins?▼

You need to review an implementation plan before coding begins when you want to ensure adherence to design documents and prevent architectural fragility, acting as a validation step prior to feature development.

What are the limitations of plan validation for complex software designs?▼

Plan validation limitations depend on the available source-of-truth documents; without comprehensive milestone documents, RFCs, and accurate ticket specifications, identifying deviations and architectural fragility in complex software designs may be incomplete.