check

Resolve spec bead open questions, conflicts, and dependencies with decisions.

8|1|Updated Jan 21, 2024
One-click install
npx skills add https://github.com/azigler/dotfiles --skill check-azigler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check
Source: https://github.com/azigler/dotfiles/tree/main/agents/skills/check
Command: npx skills add https://github.com/azigler/dotfiles --skill check-azigler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you walk a spec’s open questions, cross-spec conflicts, and dependencies and turn them into explicit decisions on the same spec bead, so downstream /test and /impl can proceed with a clean, agreed baseline.

Core Features & Use Cases

  • Open question resolution (OQs): Reviews items from Section 6 of a spec bead and records outcomes like ACCEPT, MODIFY, or DEFER.
  • Conflict and dependency alignment: Detects cross-spec inconsistencies and mismatches in ordering/interface contracts, then records resolutions or identifies needed spec updates.
  • Implementation Readiness handoff: Produces a readiness summary artifact on the spec bead when key blockers are resolved, enabling deterministic sequencing for /test and /impl.

Quick Start

Ask the AI to check the open questions and conflicts for a given spec bead, for example: "check all P1 on bd-XXXX and resolve any conflicts and dependencies."

Frequently Asked Questions about check

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

FAQPage Schema
How do I resolve open questions in a spec before implementation?

To resolve open questions in a spec, review items from Section 6 of the spec bead and record outcomes like ACCEPT, MODIFY, or DEFER directly on the bead. This ensures downstream implementation proceeds with a clean, agreed baseline.

What is the best way to track cross-spec conflicts and dependency alignment?

Tracking cross-spec conflicts involves detecting inconsistencies and mismatches in ordering or interface contracts across related beads. Resolutions are recorded directly on the spec bead to align dependencies before moving to implementation.

How do I batch triage spec open questions by priority?

Batch triage spec open questions by filtering items into P1, P2, and P3 priority levels. You can request a review of specific priorities on a bead, guiding decision-making sequentially for each item.

When do I need to generate an implementation readiness summary?

You need an implementation readiness summary when P1 blockers on a spec bead are cleared. This produces a readiness artifact on the bead, enabling deterministic sequencing for downstream testing and implementation phases.

Does spec review require loading the full context of related beads?

Yes, spec review requires loading the full spec context and related beads. This allows the system to present each open question and conflict with concrete analysis before appending decisions to the spec bead's notes.

Can I update spec bead notes without losing existing decision context?

Yes, you can update spec bead notes without losing context by using a single replace update. This update is composed from existing notes, appending new decisions while preserving the full history of resolutions.