decision

Capture routine decisions as structured light ADRs during code reviews.

3|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/ForgePlan/marketplace --skill decision-forgeplan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decision
Source: https://github.com/ForgePlan/marketplace/tree/main/plugins/fpl-skills/skills/decision
Command: npx skills add https://github.com/ForgePlan/marketplace --skill decision-forgeplan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps users quickly capture routine decisions as light ADRs (Architecture Decision Records), ensuring that the rationale behind decisions is documented and accessible for future reference.

Core Features & Use Cases

  • Light ADR Creation: Simplified process for recording decisions in a structured format.
  • Decision Triggers: Automatically triggered by specific commands or phrases.
  • Use Case: When a developer makes a routine decision during a code review or while working on a feature, this Skill can be used to quickly document the decision and its reasoning.

Quick Start

Use the /decision command to record a decision you've just made.

Frequently Asked Questions about decision

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

FAQPage Schema
How do I document routine code review decisions as light ADRs?

You can document routine code review decisions as light ADRs by triggering the capture process with a specific command or phrase. This generates a structured Architecture Decision Record with minimal input, preserving the rationale for future reference.

What is a lightweight Architecture Decision Record and when do I need one?

A lightweight Architecture Decision Record is a simplified format for capturing the rationale behind routine development choices. You need it during code reviews or feature development to quickly document decision context and reasoning without administrative overhead.

How do I capture a decision during feature development without leaving my workflow?

You capture a decision during feature development by using the /decision command. This triggers a quick capture process that requires minimal user input, automatically generating a structured ADR for documentation and future reference.

Does this ADR documentation approach work for routine decisions or only major architectural changes?

This ADR documentation approach is specifically designed for routine decisions made during code reviews or feature development. It provides a lightweight, simplified process for recording these frequent choices rather than focusing on major architectural changes.

What is the best way to ensure decision documentation happens without slowing down code reviews?

The best way to ensure decision documentation happens without slowing down code reviews is to use command-triggered, light ADR creation. This requires minimal user input and captures the structured details immediately, facilitating quick decision capture.