skills.rest
autopus-ai
autopus-aiOFFICIAL
Explore all skills by this author →
GitHub

auto-why

Traces decision rationale across Lore, SPEC, and ARCHITECTURE documents.

111|73|Updated Mar 20, 2026
Search Tags:#architecture#documentation search#omp#codebase onboarding#decision rationale#spec tracing
One-click install
npx skills add https://github.com/autopus-ai/autopus-adk --skill auto-why-autopus-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auto-why
Source: https://github.com/autopus-ai/autopus-adk/tree/main/.omp/skills/auto-why
Command: npx skills add https://github.com/autopus-ai/autopus-adk --skill auto-why-autopus-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working in a large project, it is often unclear why a particular design or implementation decision was made. This Skill searches the project's decision records so you can recover the reasoning behind past choices without manually digging through documentation. ## Core Features & Use Cases - Decision Rationale Lookup: Searches Lore, SPEC, and ARCHITECTURE files to find why a specific decision was made. - Evidence Citation: Quotes the source files and the recorded reasons so answers are grounded in project documentation. - Use Case: You inherit a codebase and wonder why OAuth2 was chosen over session-based auth. Invoke the skill with your question and it traces the decision through the project's SPEC and ARCHITECTURE records, citing the relevant passages. ## Quick Start Ask the agent to run /auto why followed by your question, for example: why was OAuth2 chosen for authentication.

Frequently Asked Questions about auto-why

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

FAQPage Schema
How do I find out why a design decision was made in my project?▼

Invoke the skill with /auto why followed by your question. It searches the project's Lore, SPEC, and ARCHITECTURE documents and returns the recorded rationale with citations to the source files.

What documents does auto-why search for decision rationale?▼

It searches three documentation sources: Lore, SPEC, and ARCHITECTURE files in the target directory. Results include citations of the relevant files and the recorded reasons for each decision.

Can I use auto-why with Claude Code or only OMP?▼

The skill declares omp compatibility and is invoked via /auto why or /auto-why entrypoints. It relies on workspace search tools, so it works in agent environments that provide equivalent file search capabilities.

What happens if no decision record exists for my question?▼

The skill depends on existing Lore, SPEC, and ARCHITECTURE documentation. If the decision was never recorded in those files, there is no rationale to trace, so keeping decision records up to date is a prerequisite.

Related Skills

Explore More Software Engineering Skills→
dotCMSdotCMS
950

speckit-adr-context

Retrieves relevant Architecture Decision Records from dotCMS/platform-adrs to inform feature planning.

Official
Intermediate
DazlarusDazlarus

revision

Revises existing plans using PLAN REVISION tags while preventing scope drift into new tasks.

Community
Intermediate
n8n-ion8n-io
203.0k

n8n:spec-driven-development

Synchronize implementation code with architectural specification documents throughout the development lifecycle.

Official
Intermediate
iankikuiankiku
18

team-memory

Analyzes commits, pull requests, and team discussions to compile a project memory file.

Community
Advanced