Skill

list-tech-specs

Lists technical specifications from tech-specs/ directories with status (DRAFT, APPROVED, REFERENCE), metadata, filters by status/RFC, and table/list output. Useful for tracking architecture docs.

documentation

cli-tools

npx claudepluginhub jpoutrin/product-forge --plugin devops-data

Tool Access

This skill uses the workspace's default tool permissions.

Preview

**Category**: Technical Architecture

SKILL.md

Similar Skills

spec-conventions

Provides conventions for writing self-contained, implementation-ready spec documents. Distinguishes specs from docs; covers structure including data model, architecture, security, operations, scope, and deliverables.

1 file

sorah-spec

rfc

Manages architecture RFCs: create populated drafts from conversation and docs context, review existing, list all, update sections, transition status.

5 files

doc

status

Displays dashboard of specification status from .specs/ directory, including workflow progress, quality scores, pending items, and issues. Useful for tracking spec-driven development workflows with --all or spec-id.

4 tools

spec-driven-development

Stats

Parent Repo Stars7

Parent Repo Forks0

Last CommitFeb 4, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

list-tech-specs

Category: Technical Architecture

Usage

/list-tech-specs [options]

Options

Option	Description
`--status <status>`	Filter by status (DRAFT, APPROVED, REFERENCE)
`--all`	Include archived specs
`--rfc <RFC-XXXX>`	Filter by linked RFC
`--format table	list`

Execution Instructions

When this command is run, Claude Code should:

Scan Tech Spec Directories

tech-specs/
├── draft/      → DRAFT
├── approved/   → APPROVED
├── reference/  → REFERENCE
└── archive/    → (only with --all)

Extract Metadata from Each Spec
- Tech Spec ID (from filename or frontmatter)
- Title
- Status
- Author
- Linked RFC (if any)
- Created date
- Last updated date
Apply Filters (if specified)
- Filter by status
- Filter by linked RFC
- Exclude archive unless --all
Display Results

Table Format (default)

Tech Spec Summary
=================

Active: 8 | Reference: 15 | Archived: 5

| Spec ID   | Title                      | Status    | RFC Link  | Updated    |
|-----------|----------------------------|-----------|-----------|------------|
| TS-0045   | Payment Gateway API        | APPROVED  | RFC-0042  | 2025-12-05 |
| TS-0044   | User Auth Implementation   | DRAFT     | -         | 2025-12-04 |
| TS-0043   | Cache Layer Design         | REFERENCE | RFC-0038  | 2025-12-01 |
| TS-0042   | Search Service             | APPROVED  | -         | 2025-11-28 |

Use '/tech-spec-status TS-XXXX' to see details or update status.

List Format

TS-0045: Payment Gateway API
  Status: APPROVED
  Author: Jane Doe
  RFC: RFC-0042
  Created: 2025-12-01
  Updated: 2025-12-05
  Location: tech-specs/approved/TS-0045-payment-gateway-api.md

TS-0044: User Auth Implementation
  Status: DRAFT
  Author: John Doe
  RFC: -
  ...

Status Summary

Always show a summary at the top:

Tech Spec Status Summary
========================
DRAFT:     3
APPROVED:  5
REFERENCE: 15
ARCHIVED:  5 (use --all to include)

Sorting

Default sort order:

DRAFT (work in progress)
APPROVED (ready to implement)
REFERENCE (implemented)

Within each status, sort by last_updated (newest first).

Example Usage

# List all active tech specs
/list-tech-specs

# List only specs in draft
/list-tech-specs --status DRAFT

# List specs linked to specific RFC
/list-tech-specs --rfc RFC-0042

# List all including archived
/list-tech-specs --all

Empty State

If no Tech Specs exist:

No Technical Specifications found.

To create a new Tech Spec:
  /create-tech-spec <title>

Tech Spec documentation:
  See plugins/devops-data/skills/technical-specification/SKILL.md

Error Handling

If tech-specs/ directory doesn't exist, show empty state message
If spec file has invalid frontmatter, show warning but continue
Handle missing metadata gracefully (show "N/A")