decisions

Name: decisions
Availability: InStock
Author: Telefrek

Manage architecture decisions through query, revisit, evaluation, deferment, closure, and roadmap planning.

Updated Aug 23, 2026

Search Tags:#knowledge base #strategic planning #team collaboration #architecture decision #decision management

Ready to run

npx skills add https://github.com/telefrek/jlsm --skill decisions-telefrek

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: decisions
Source: https://github.com/telefrek/jlsm/tree/main/.claude/skills/decisions
Command: npx skills add https://github.com/telefrek/jlsm --skill decisions-telefrek

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill unit streamlines architecture decision management, helping teams track, review, and update decisions efficiently, ensuring alignment and continuous improvement.

Core Features & Use Cases

Decision Query: Easily retrieve information about specific decisions using natural language.
Decision Revisit and Evaluation: Revisit past decisions, check conditions, and deliberate on updates.
Decision Deferment and Closure: Park or permanently rule out topics for future consideration.
Roadmap Planning: Cluster, classify, and prioritize deferred decisions for strategic planning.
Triage Review: Process and manage deferred items to keep the decision backlog up-to-date.

Quick Start

Use the decisions skill to query a decision like "What did we decide about the database?"

Frequently Asked Questions about decisions

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

FAQPage Schema

How do I manage architecture decisions across different project stages?▼

Architecture decision management tracks decisions from initial query through revisit, deferment, closure, and roadmap planning. It uses a structured repository of decision records to facilitate team alignment and continuous improvement throughout the lifecycle.

What is the best way to query past architecture decisions using natural language?▼

Querying past architecture decisions supports natural language inputs, allowing you to retrieve specific records like database choices. The system searches a structured repository to return relevant historical context and deliberation details.

How do I handle deferred architecture decisions for future roadmap planning?▼

Deferred architecture decisions are clustered, classified, and prioritized for strategic roadmap planning. A triage review process manages these parked items to keep the decision backlog updated and ensure future alignment.

Do I need a specific directory structure to track architecture decision records?▼

Tracking architecture decision records requires a well-defined directory structure and a SKILL.md entry point for operation. This setup ensures the repository can accurately store, retrieve, and manage the context needed for team collaboration.

When should I revisit and evaluate past architecture decisions?▼

Revisit and evaluate past architecture decisions when project conditions change or updates are needed. The process checks previous conditions and deliberates on modifications to ensure the technical choices remain valid and aligned.

Can I permanently rule out architecture topics from future consideration?▼

Architecture topics can be permanently ruled out from future consideration through the decision closure feature. This parks or eliminates deferred items, keeping the decision backlog clean and focused on active strategic planning.