capture

Capture technical decisions from sessions into standardized Architectural Decision Records.

Updated Nov 15, 2025
One-click install
npx skills add https://github.com/cloudvoyant/claudevoyant --skill capture-cloudvoyant
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: capture
Source: https://github.com/cloudvoyant/claudevoyant/tree/main/plugins/adr/skills/capture
Command: npx skills add https://github.com/cloudvoyant/claudevoyant --skill capture-cloudvoyant

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you systematically document significant technical decisions made during a development session, ensuring that important architectural choices are recorded and retrievable.

Core Features & Use Cases

  • Decision Capture: Analyzes conversation history to identify and extract key technical decisions.
  • ADR Generation: Creates Architectural Decision Records (ADRs) in a standardized format.
  • Use Case: After a team discussion about choosing a new database, use this Skill to automatically generate an ADR documenting the decision, the context, and the alternatives considered.

Quick Start

Use the capture skill to document the technical decisions made in this session.

Frequently Asked Questions about capture

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

FAQPage Schema
How do I document technical decisions from a development session into an ADR?

To document technical decisions into an ADR, this Skill analyzes your conversation history to extract key architecture choices and generates a standardized Architectural Decision Record capturing the context and alternatives considered.

What is an Architectural Decision Record and when do I need one?

An Architectural Decision Record is a standardized document capturing significant technical decisions. You need one when making technology choices, architecture changes, or process modifications within software development projects to ensure decisions are recorded and retrievable.

Can I automatically generate architecture documentation from a team discussion about choosing a new database?

Yes, you can automatically generate architecture documentation from a team discussion. The Skill extracts the database technology choice, decision context, and evaluated alternatives from the session content and formats them into a predefined ADR template.

What's the best way to capture process modifications and technology choices for knowledge management?

The best way to capture process modifications and technology choices for knowledge management is to use a Skill that analyzes conversation content to identify significant technical decisions and records them using a standardized ADR format for future retrieval.

Does this ADR generation tool require a specific template or manual input to document technical decisions?

This ADR generation tool requires adherence to a predefined ADR template. It analyzes conversation content automatically to extract decisions, meaning no manual input is needed beyond the initial session discussion about technology choices and architecture changes.

What types of technical decisions are suitable for capture into Architectural Decision Records?

Suitable technical decisions for capture include technology choices, architecture changes, and process modifications within software development projects. The Skill analyzes session content to identify significant decisions and records them into standardized Architectural Decision Records.