pending

Lists open VALIDAR DEPOIS items and unimplemented TRD tasks across SDD pipeline artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? In a spec-driven development pipeline, validation questions marked "VALIDAR DEPOIS" and unfinished tasks accumulate across many artifacts (PRD, TRD, code review, QA report, security review, SRE review, BASELINE). Manually opening each file to find what is still pending is slow and error-prone. This Skill scans all of them at once and returns two consolidated tables: open validation items and tasks not yet marked as implemented. ## Core Features & Use Cases - Pending validation scan: Extracts every "VALIDAR DEPOIS" item with status "pendente" from all feature specs and docs/BASELINE.md, deduplicating rows that merely reference a previous round. - Unimplemented task report: Reads the "Decomposição de tarefas e dependências" table of each TRD and lists rows whose Status is still pendente, em andamento, or bloqueado, including the linked GitHub issue. - Guided resolution: Routes each item to the right follow-up — /btt-sdd:amend to close a validation item, /btt-sdd:implement for pending tasks, or /btt-sdd:trd when a feature has a PRD but no TRD yet. - Use Case: Before a sprint review, ask what is still pending; the Skill returns a table like "feature | artifact | ID | question | context" plus the open task list, so you can decide what to resolve or implement next. ## Quick Start Ask the assistant to list all pending validation items and unimplemented tasks across the SDD pipeline, optionally naming a specific feature slug to filter the results.

Frequently Asked Questions about pending

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

FAQPage Schema
How do I list all pending validation items in an SDD pipeline?▼

Run the sdd-pending script from the project root, optionally passing a feature slug to filter results. It scans prd.md, trd.md, review artifacts, and docs/BASELINE.md, returning a deduplicated table of items still marked pendente.

How do I find tasks not yet implemented in a TRD decomposition table?▼

The script parses the "Decomposição de tarefas e dependências" section of each trd.md and lists rows whose Status is pendente, em andamento, or bloqueado. Status and Issue GitHub columns are located by header text, so column order variations do not break detection.

Does the pending script work on Windows PowerShell?▼

Yes, a PowerShell version (sdd-pending.ps1) is provided alongside the bash script with equivalent behavior. It accepts an optional -Slug parameter and avoids accented characters in source to prevent codepage parsing issues on Windows PowerShell 5.1.

How do I resolve a VALIDAR DEPOIS item once I have the answer?▼

Collect the answer and route it through the /btt-sdd:amend skill, which records the resolution in the correct artifact with a consistent revision log. Do not edit the artifact directly outside that flow.

Why does the pending report show a feature with no tasks listed?▼

Features with an approved prd.md but no trd.md yet have no decomposed tasks, so they appear in a separate "specs without TRD" note. The next step for those is running the TRD skill before implementation tasks can be tracked.