status

Reports the current pipeline stage of each feature in the specs directory.

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/asengardeon/btt-sdd-pipeline --skill status-asengardeon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/asengardeon/btt-sdd-pipeline/tree/main/plugins/btt-sdd/skills/status
Command: npx skills add https://github.com/asengardeon/btt-sdd-pipeline --skill status-asengardeon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? In a spec-driven development pipeline where each feature moves through PRD, TRD, implementation, code review, QA, security, and SRE stages, it is hard to know at a glance where each feature stands. This Skill reads the artifacts under specs/ and summarizes the current stage, next command, pending validation items, and revalidation flags for every feature without loading each artifact into context. ## Core Features & Use Cases - Pipeline status table: Runs a helper script (Bash or PowerShell) that prints, per feature, the current stage, the next pipeline command, the count of open VALIDAR DEPOIS items, and whether any stage requires revalidation. - Verdict and approval detection: Distinguishes approved artifacts from drafts, detects rejected review verdicts, recognizes formally skipped QA, and cross-checks TRD task status (including PR merge state via gh) before declaring the pipeline complete. - Docs drift check: With the --check-docs flag, compares the project's docs/*.md files against the scaffold of the installed plugin version and flags divergences without applying any automatic merge. - Use Case: After a week of parallel work on three features, ask for a status overview to see which feature is blocked on a failed security review, which has pending validation items, and which is ready for the SRE stage. ## Quick Start Ask the assistant to show the current stage of all features in specs/ using the status skill, optionally naming a single feature slug to inspect.

Frequently Asked Questions about status

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

FAQPage Schema
How do I check the status of features in a spec-driven development pipeline?▼

Run the status skill, which executes the sdd-status script over the specs/ directory. It prints a table with each feature's current stage, the next pipeline command, pending validation count, and any revalidation flags, without reading every artifact in full.

How do I see the status of only one feature?▼

Pass the feature's slug as an argument to the script, for example sdd-status.sh my-feature or sdd-status.ps1 -Slug my-feature. The output then covers only that feature instead of every directory under specs/.

Does the status script work on Windows PowerShell?▼

Yes, the skill ships both a Bash script (sdd-status.sh) and a PowerShell equivalent (sdd-status.ps1) with the same behavior. The PowerShell version avoids accented characters in its source so it parses correctly under Windows PowerShell 5.1 without a BOM.

Why does the status table show a stage as requiring revalidation?▼

A revalidation flag appears when an artifact's revision log contains a 'requer revalidação' entry, typically created by the amend command, that is newer than the latest formal re-approval of the target PRD or TRD. Once the target artifact is re-approved with a later date, the flag clears.

Why does the script say the verdict was not identified for a review artifact?▼

The script parses verdicts by convention: the last row of the approval history table or bold text under the general verdict heading. If an artifact deviates from that format, the script reports 'verdict not identified' and the agent falls back to reading the full file.

Can the status skill detect outdated project documentation?▼

Yes, running it with the --check-docs flag (or -CheckDocs in PowerShell) compares each docs/*.md file in the project against the scaffold shipped with the installed plugin version. It only reports divergences and never merges or modifies files automatically.