Can I track the status of my architectural decisions?

Yes, the skill is designed to manage ADR statuses such as proposed, accepted, superseded, or deprecated, allowing teams to see the current evolution of the system design.

How does this skill link documentation to tasks?

It utilizes the workbench.ps1 command-line interface to associate specific ADRs or architecture files with unique work item IDs, ensuring documentation is tied to project execution.

Does it support automatic backlinking?

The skill includes a sync workflow that automatically updates and maintains backlinks across all architecture documents and work items to ensure a connected knowledge base.

What is an ADR in the context of this skill?

ADR stands for Architecture Decision Record. It is a document that captures an important architectural decision, including its context, rationale, and consequences for future reference.

Workbench Architecture

Name: Workbench Architecture
Author: bravellian

bybravellian

Collaboration Tools

Manages system design documentation and Architecture Decision Records (ADRs) within the Workbench CLI environment.

About

The workbench-architecture skill streamlines the process of documenting system design and tracking architectural decisions through the Workbench CLI. It enables developers to create structured architecture overviews and ADRs with consistent front matter, link these documents to specific work items, and maintain a history of project rationale. By automating backlink synchronization and status tracking for decisions (proposed, accepted, superseded), it ensures that technical debt and design intent remain visible and searchable throughout the software development lifecycle.

Key Features

Template-based system architecture documentation
Lifecycle management for decision statuses (proposed, accepted, superseded)
0 GitHub stars
Automated backlink synchronization across the doc set
Standardized creation of Architecture Decision Records (ADRs)
Bi-directional linking between documentation and work items

Use Cases

Mapping complex subsystem flows to specific task IDs and project requirements
Maintaining a searchable audit trail of technical decisions for team onboarding
Documenting the rationale behind major technology stack shifts or library choices

About

Key Features

Template-based system architecture documentation
Lifecycle management for decision statuses (proposed, accepted, superseded)
0 GitHub stars
Automated backlink synchronization across the doc set
Standardized creation of Architecture Decision Records (ADRs)
Bi-directional linking between documentation and work items

Use Cases

Mapping complex subsystem flows to specific task IDs and project requirements
Maintaining a searchable audit trail of technical decisions for team onboarding
Documenting the rationale behind major technology stack shifts or library choices