Menú
Quick overview of the decision log state — counts by status, recent decisions, and run tracking info.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Implement one or more proposed decisions. Makes code changes, adds `@decision` annotations, and updates decision status.
Implement one or more proposed decisions. Makes code changes, adds `@decision` annotations, and updates decision status.
Resolve decision ID collisions between a local branch and the base branch (and open PRs) before rebasing. Renames colliding local decisions with git mv, rewrites cross-references and annotations, then squashes branch commits into a single rebase-clean reindex commit.
Shared utility scripts for DLD skills. Not intended for direct invocation — used internally by other DLD skills.
Resolve decision ID collisions between a local branch and the base branch (and open PRs) before rebasing. Renames colliding local decisions with git mv, rewrites cross-references and annotations, then squashes branch commits into a single rebase-clean reindex commit.
Autonomous audit — detects drift, fixes issues, and opens a PR. Designed for scheduled/CI execution without human interaction.
| name | dld-status |
| description | Quick overview of the decision log state — counts by status, recent decisions, and run tracking info. |
| user_invocable | true |
You are generating a quick overview of the decision log state for the developer.
This skill has no dedicated scripts. It reads decision files and state files directly:
dld.config.yaml — project configuration (decisions directory, mode)decisions/records/DL-*.md — all decision records (scan YAML frontmatter for status, tags, timestamp, namespace)decisions/.dld-state.yaml — run tracking state for audit and snapshot (may not exist)Check that dld.config.yaml exists at the repo root. If not, tell the user to run /dld-init first and stop.
dld.config.yaml to understand the project structure (flat vs namespaced, decisions directory)decisions/records/) to gather statisticsScan all DL-*.md files in the records subdirectory (decisions/records/, including namespace subdirectories). Read the status field from each file's YAML frontmatter. Count:
proposedaccepteddeprecatedsupersededPresent as:
## Decision Log Status
| Status | Count |
|--------|-------|
| proposed | 3 |
| accepted | 12 |
| deprecated | 2 |
| superseded | 1 |
| **Total** | **18** |
Show the 5 most recent decisions (by timestamp), with ID, title, status:
## Recent Decisions
| ID | Title | Status | Date |
|----|-------|--------|------|
| DL-018 | ... | proposed | 2026-03-07 |
| DL-017 | ... | accepted | 2026-03-06 |
| ...
Namespaced projects: Show decision counts per namespace.
## By Namespace
| Namespace | Total | Proposed | Accepted |
|-----------|-------|----------|----------|
| billing | 8 | 1 | 7 |
| auth | 5 | 2 | 3 |
| shared | 5 | 0 | 5 |
All projects: If there are tags in use, show the most active tags (those with the most decisions):
## Active Tags
| Tag | Decisions |
|-----|-----------|
| payment-gateway | 4 |
| auth-refactor | 3 |
Read decisions/.dld-state.yaml if it exists. Report:
If the file doesn't exist, note that no audits or snapshots have been run yet.
## Run History
- **Last audit:** 2026-03-06 at commit `a1b2c3d` (1 day ago)
- **Last snapshot:** 2026-03-05 (2 days ago, covers through DL-015)
Or:
## Run History
No audits or snapshots have been run yet. Use `/dld-audit` to check for drift.
If there are any proposed decisions, list them as a call to action:
## Pending Implementation
These decisions are proposed but not yet implemented:
- **DL-016**: Rate limiting strategy
- **DL-017**: Cache invalidation approach
- **DL-018**: Error response format
Use `/dld-implement DL-NNN` to implement them.