Inspiration
I work as a tech lead, and my project folders fill up with specs, ADRs, and several versions of the same business rules. When a rule changes, the hard question is which earlier decisions were written against the old version. Answering it means rereading everything. I hate that part of the job. I started out wanting to tidy a messy folder and realized the sorting only mattered if it helped answer that question.
What it does
You point the Skill at one project folder. It sorts the documents into ADRs, Business Rules, Specs, and Miscellaneous after you approve the plan. It then works out which business rules version is the previous one and which is current, lists what changed with exact quotes, and shows which ADRs and specs relied on the changed rules. It saves an impact report, proposed ADR drafts, and a review action list. Every statement cites its source file, and where the documents are silent it writes an open question.
How we built it
The Skill is a Markdown workflow written to the Uliya Skill Development Standard with the UGOS Skill Creation Tool. It delegates to four registered experts across 11 steps in two phases: file-agent, document-agent, knowledge-agent, and photo-agent. I used Claude to explore ideas, draft the Skill files, and run the static check. The design went through several versions, from a Downloads sorter to a knowledge vault to the current change-impact workflow.
Challenges we ran into
- I don't have a NAS, so everything I did is unverified at runtime.
- The hackathon for skills can't contain scripts, which made this a little bit harder since everything has to be delegated to "experts".
- I tried to make an all-in-one solution. My first idea is to generate ADRs, requirements, and tickets from everything. Narrowing it to one triggering event and one checkable result was extremely hard for some reason.
- Deciding which rules file is newer without asking the user turned out to be unreliable, so the Skill proposes a pair and asks for confirmation.
Accomplishments that we're proud of
- The only required input is the project folder.
- Findings are split into documents that cite the rule and documents that only repeat its old wording, so nothing is reported on similarity alone.
- Drafts never invent a decision. The Decision section stays open for the architect.
- The package passes the official static checker with no errors or warnings.
What we learned
Basically, I learned what a skill is, how to build it further, and how to enforce some level of quality within the Skill being created.
What's next for Decision File Impact
- Build the synthetic test project and run the two core tests and the edge case on a real UGREEN AI NAS.
- Tune the instructions based on what the experts return in practice.
- Flag superseded decisions that live specs still cite.
- Generate an onboarding reading order from the references between documents.
Built With
- claude
- ugreen
