podcast-adrian

Make and document an architectural or technical decision before writing code. Run /architect for a meaningful choice between approaches, a feature or page designed from scratch, a stack decision, or when /develop says a decision is owed. Acts as a Staff/Principal engineer: challenges bad directions, asks deep feature-specific questions, recommends rather than lists, then writes a complete-build-spec ADR to docs/adr/ for confirmation. Owns all ADR files.

Bootstrap accurate project context by writing the AGENTS.md files. Run /audit once on a new project (after the stack is chosen and scaffolded) to capture conventions and tooling choices, or on an existing codebase to scan it and write root + nested AGENTS.md context files so every later skill and AI tool knows the real project. Gap-fills partially documented repos without clobbering curated content.

Use this skill to find and fix the root cause of a bug: something failing, broken, throwing, or behaving wrong. Run /debug when a test fails for a non-obvious reason, when a check finds a failure, or when behavior is unexpected. It runs a disciplined loop (reproduce, localize, hypothesize, test, fix at the root, verify), one hypothesis at a time until the cause is proven, then makes the minimal fix and hands a regression test to /test. It fixes the cause, not the symptom; no features or extra refactors.

Build a feature (UI or logical/backend) from an approved design. Run /develop to implement a page, component, API, service, data layer, or slice. Gates on the decision first: if building would require inventing something undecided (a design system, page composition, a provider, a data model, a feature's behavior) with no ADR recording it, /develop stops and routes to /architect. Otherwise it reads the ADR + AGENTS.md (+ design.md for UI), builds, proves the result runs, and advances the roadmap.

Stress-test a change against production-only failure modes: edge cases, concurrency, scale, security. Run /harden after the code works and is tested, typically the last step before merge on medium/full tier. A systems-level subagent audits the diff against a threat rubric and writes a prioritized hardening checklist; nothing is edited without approval.

Turn an idea into a living, coarse feature roadmap, or keep an existing one current. Run /roadmap with a product idea (plan), with a single feature (add one row), or bare after shipping (replan/reconcile). Writes docs/roadmap/: ordered, weighted features with intent and acceptance-criteria seeds, foundations first, sliced by a chosen build approach. Owns all roadmap files.

Keep durable knowledge current after a change ships. Run /sync as the last step on medium/full work, around merge. Updates AGENTS.md context files (root + nested) to reflect what changed, reconciles the feature's roadmap row and its ADR Status line, creates a nested AGENTS.md for a genuinely new area, and cleans orphans after deletions.

Write a test suite for code just built or changed. Run /test after implementing a feature, component, API route, or fix; it targets the changed-and-uncommitted files (working tree + staged + untracked), classifies each, and writes the right kind of test (unit, component, integration, E2E candidate) via a subagent, honoring the project's test tooling and preferences.