agentleFS
Sign inStart free
buildpad-aibuildpad-ai/skills/buildpad-spec-status/SKILL.md

buildpad-spec-status

Skill1 starsChanged 28 days agoMITView on GitHub

Show specification status and progress

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 4 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read .kiro/specs/$ARGUMENTS/spec.json for metadata and phase status

    line 20
  2. Very specific:

    Read .kiro/specs/$ARGUMENTS/brief.md if it exists

    line 21
  3. Very specific:

    Read existing files: requirements.md, design.md, tasks.md (if they exist)

    line 22
  4. Very specific:

    Check .kiro/specs/$ARGUMENTS/ directory for available files

    line 23
  5. Very specific:

    Read .kiro/steering/roadmap.md if it exists and this spec appears in it

    line 24
  6. Distinctive:

    Design: Check for architecture, components, diagrams, and whether boundary sections are present

    line 30
  7. Very specific:

    Approvals: Check approval status in spec.json

    line 32
  8. Distinctive:

    Call out when the current spec shape looks too broad and may want roadmap/design splitting instead of more local repair

    line 39
  9. Very specific:

    Create report in the language specified in spec.json covering:

    line 43
  10. Distinctive:

    Task Breakdown: If tasks exist, show completed/remaining counts

    line 46
  11. Distinctive:

    Run with no argument or use wildcard

    line 69

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

buildpad-spec-status Skill

Core Mission

  • Success Criteria:
    • Show current phase and completion status
    • Identify next actions and blockers
    • Provide clear visibility into progress
    • Surface boundary readiness, upstream/downstream context, and likely revalidation needs when available

Execution Steps

Step 1: Load Spec Context

  • Read .kiro/specs/$ARGUMENTS/spec.json for metadata and phase status
  • Read .kiro/specs/$ARGUMENTS/brief.md if it exists
  • Read existing files: requirements.md, design.md, tasks.md (if they exist)
  • Check .kiro/specs/$ARGUMENTS/ directory for available files
  • Read .kiro/steering/roadmap.md if it exists and this spec appears in it

Step 2: Analyze Status

Parse each phase:

  • Requirements: Count requirements and acceptance criteria
  • Design: Check for architecture, components, diagrams, and whether boundary sections are present
  • Tasks: Count completed vs total tasks (parse - [x] vs - [ ])
  • Approvals: Check approval status in spec.json
  • Boundary context:
    • From brief.md: note Boundary Candidates, Upstream / Downstream, and Existing Spec Touchpoints if present
    • From design.md: note Boundary Commitments, Out of Boundary, Allowed Dependencies, and Revalidation Triggers if present
    • From roadmap.md: note upstream dependencies and whether this spec is adjacent to Existing Spec Updates
  • Revalidation watchlist:
    • Identify downstream specs, neighboring existing-spec updates, or rollout-sensitive design notes that may need revalidation if this spec changes
    • Call out when the current spec shape looks too broad and may want roadmap/design splitting instead of more local repair

Step 3: Generate Report

Create report in the language specified in spec.json covering:

  1. Current Phase & Progress: Where the spec is in the workflow
  2. Completion Status: Percentage complete for each phase
  3. Task Breakdown: If tasks exist, show completed/remaining counts
  4. Boundary Context: Upstream/downstream, out-of-boundary, and allowed dependency notes when available
  5. Revalidation Watchlist: Downstream or adjacent work likely affected by changes to this spec
  6. Next Actions: What needs to be done next
  7. Blockers: Any issues preventing progress

Format: Clear, scannable format with emojis for status

Safety & Fallback

Error Scenarios

Spec Not Found:

  • Message: "No spec found for $ARGUMENTS. Check available specs in .kiro/specs/"
  • Action: List available spec directories

Incomplete Spec:

  • Warning: Identify which files are missing
  • Suggested Action: Point to next phase command

List All Specs

To see all available specs:

  • Run with no argument or use wildcard
  • Shows all specs in .kiro/specs/ with their status

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free