skills.rest
Sermilion
SermilionCOMMUNITY
Explore all skills by this author →
GitHub

bill-boundary-decisions

Capture architectural decision rationale in a module's decisions.md file.

13|1|Updated Mar 16, 2026
Search Tags:#architecture#documentation#decisions#traceability#software-design#boundary#decisions.md
One-click install
npx skills add https://github.com/Sermilion/skill-bill --skill bill-boundary-decisions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bill-boundary-decisions
Source: https://github.com/Sermilion/skill-bill/tree/main/skills/bill-boundary-decisions
Command: npx skills add https://github.com/Sermilion/skill-bill --skill bill-boundary-decisions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams capture the rationale behind architectural or implementation decisions in a module, package, or area, ensuring context persists alongside code changes.

Core Features & Use Cases

  • Structured decision entries: each entry captures date, title, context, decision, and reason in a consistent format.
  • Boundary-focused logs: designed to document why a boundary or constraint was chosen and how it affects modules.
  • Lifecycle guidance: supports newest-first ordering, pruning when decisions are reversed, and clear separation from feature history.

Quick Start

Create or update the file at <primary-boundary>/agent/decisions.md and add a new decision entry describing your context, decision, and rationale.

Frequently Asked Questions about bill-boundary-decisions

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

FAQPage Schema
How do I document architectural decisions in my codebase?▼

Documenting architectural decisions involves capturing the rationale in a decisions.md file. You add structured entries containing the date, title, context, decision, and reason to maintain traceability alongside your code.

What is a boundary decision log in software design?▼

A boundary decision log records why a specific architectural boundary was chosen and how it affects modules. It uses a structured format to separate these constraints from general feature history.

How do I format a decisions.md file for traceability?▼

Format a decisions.md file by adding structured entries ordered newest-first. Each entry must contain the date, title, context, decision, and reason to maintain clear traceability of architectural choices.

When should I prune entries from an architectural decision log?▼

Prune entries from an architectural decision log when a decision is reversed. This lifecycle guidance keeps the log relevant by removing outdated choices and separating it from feature history.

Can I use a structured decision log across multiple packages?▼

Yes, you can apply structured decision logs across modules, packages, or areas. The log enforces consistent file-path conventions and entry formats regardless of the specific boundary being documented.

Related Skills

Explore More Software Engineering Skills→
zerobias-orgzerobias-org

monorepo-structure

Define standard monorepo module layouts with package/{vendor}/{module} paths.

Official
Intermediate
netguy204netguy204
3

decision-create

Generate template-conformant decision entries for docs/trunk/DECISIONS.md.

Community
Intermediate
buYoungbuYoung
18

feature-design-doc

Draft, update, and fact-check Feature Design Docs against a fixed template.

Community
Advanced
slashwhyslashwhy
5

architectural-documentation

Generate templates for implementation plans, ADRs, API specifications, and migration guides.

Official
Basic