arch-skill

Route architecture tasks to /prompts:* commands and enforce a single docs/ canonical plan.

2|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/aelaguiz/arch_skill --skill arch-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arch-skill
Source: https://github.com/aelaguiz/arch_skill/tree/main/skills/arch-skill
Command: npx skills add https://github.com/aelaguiz/arch_skill --skill arch-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Router + invariants for architecture prompts to ensure a single canonical plan and enforce a strict workflow, routing tasks to the correct prompt and keeping a central SSOT.

Core Features & Use Cases

  • Single-document rule (SSOT): exactly one canonical plan under docs/ is authoritative. The worklog is derived from it.
  • Code is ground truth: anchor claims in file paths/symbols/commands; avoid speculation.
  • Minimal verification & strict question policy: prefer existing tests/commands; avoid inventing new harnesses unless necessary.
  • Routing & on-demand loading: load the appropriate /prompts:* command or load the markdown procedure when needed, with proper placeholder binding.
  • Workflow governance: enforces the arch_skill workflow invariants and guides users to the correct prompts.

Quick Start

Ask arch-skill to route your architecture task to the correct /prompts:* command and load the canonical plan from docs/.

Frequently Asked Questions about arch-skill

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

FAQPage Schema
How do I maintain a single source of truth for architecture planning?

Routing architecture prompts works by directing tasks to the correct /prompts:* commands and loading markdown procedures on demand with proper placeholder binding, ensuring strict workflow governance and correct execution flow.

How do I route architecture prompts to the correct workflow commands?

Routing architecture prompts works by directing tasks to the correct /prompts:* commands and loading markdown procedures on demand with proper placeholder binding, ensuring strict workflow governance and correct execution flow.

What is the best way to anchor architecture claims to verify code accuracy?

The best way to anchor architecture claims is treating code as ground truth by referencing exact file paths, symbols, and commands. This avoids speculation and ensures minimal verification by preferring existing tests over inventing new harnesses.

Can I use this architecture workflow routing without adding new test harnesses?

You can use this architecture workflow routing without new test harnesses by applying a minimal verification policy. It strictly prefers existing tests and commands to validate claims, avoiding invented harnesses unless absolutely necessary.

Why does my architecture workflow require a single canonical plan in docs?

Your architecture workflow requires a single canonical plan in docs/ to satisfy workflow invariants and enforce a single source of truth. This ensures planning, research grounding, deep dives, and implementation audits remain strictly bound and consistent.