accommodation-tracker

Name: accommodation-tracker
Availability: InStock
Author: Olivier

Track workarounds, architectural deviations, and repeated failed attempts during implementation.

Updated Feb 7, 2026

Search Tags:#architecture #debugging #documentation #pattern validation #workarounds #implementation drift #post-stage audit

Ready to run

npx skills add https://github.com/thisolivier/chronolog --skill accommodation-tracker

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: accommodation-tracker
Source: https://github.com/thisolivier/chronolog/tree/main/.claude/skills/accommodation-tracker
Command: npx skills add https://github.com/thisolivier/chronolog --skill accommodation-tracker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you document unexpected workarounds, architectural deviations, and repeated failed attempts so they can be reviewed, resolved, and prevented from silently compounding across the project timeline.

Core Features & Use Cases

Post-stage accommodation audit: Capture what changed unexpectedly after a major implementation stage, including why it was necessary and what trade-offs were accepted.
On-the-fly guttering detection: Identify when you’ve tried and failed the same underlying approach 3+ times, then pause and validate the assumption before continuing.
Structured tracking and severity: Classify each accommodation by impact, effort, and severity (Low/Medium/High), and flag entries that still need community validation.

Quick Start

After finishing a major implementation stage, ask to review accommodations so the Skill can inventory deviations, record them in the appropriate docs file, and summarize what needs validation.

Frequently Asked Questions about accommodation-tracker

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

FAQPage Schema

How do I track implementation drift and document workarounds after a development stage?▼

Track implementation drift by running a post-stage accommodation audit to inventory architectural deviations and unexpected workarounds, classifying each entry by impact, effort, and severity to prevent technical debt from compounding.

What is implementation guttering and how do I detect it during troubleshooting?▼

Implementation guttering occurs when repeated troubleshooting attempts fail to resolve an issue, detectable by tracking three or more failed attempts at the same underlying approach before pausing to validate assumptions.

How do I document architectural deviations and trade-offs accepted during software engineering projects?▼

Document architectural deviations by enforcing an accommodations-file workflow that records unexpected changes, explains why they were necessary, and classifies the accepted trade-offs by severity for later review.

When should I perform a post-stage audit for unexpected workarounds?▼

Perform a post-stage audit immediately after finishing a major implementation stage to capture unexpected workarounds, record architectural accommodations, and summarize entries that still require pattern validation.

Can I use pattern validation to resolve repeated failed implementation attempts?▼

Yes, you can invoke pattern validation as an optional child process to validate assumptions and detect guttering after three or more failed implementation attempts before proceeding with further development.