ab-update-architecture

Estrelas180

Forks14

Atualizado15 de maio de 2026 às 09:52

Refresh architecture and domain documentation after impactful changes. Use when code has drifted from the documented architecture.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

ayoubben18

ayoubben18/ab-method

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	ab-update-architecture
description	Refresh architecture and domain documentation after impactful changes. Use when code has drifted from the documented architecture.

This skill runs the AB Method update-architecture workflow.

Follow the workflow defined in .ab-method/core/update-architecture.md exactly — it contains the full process, output format, and rules.

Before doing anything, check .ab-method/structure/index.yaml. It defines where this workflow reads from and writes to. Paths are user-configurable; never hardcode them.

Mais deste repositório

mesmo repositório

sync-architecture

ayoubben18/ab-method

Post-implementation documentation-sync detector. Spins up ONE read-only subagent on a completed task's diff to find everything the change introduced that the architecture docs don't yet know about — new endpoints, patterns, dependencies, domain terms, ADR-worthy decisions — routed to the exact doc each belongs in. Autonomous runs apply only append-only safe additions and defer domain/ADR reshapes; interactive runs present the proposed doc deltas to pick. Use after a task's missions are done (from create-task / start-task / start-roadmap) or standalone on a diff.

2026-07-14180

reconcile-roadmap

ayoubben18/ab-method

Cross-plan coherence critic for a whole roadmap. Reads roadmap.md plus every planned task's progress-tracker.md and pushes back ONLY on genuine discrepancies BETWEEN the finished plans — broken seams, coverage gaps, duplicated work, reversed/missing edges, terminology drift, conflicting assumptions. Read-only; silent when the plans cohere. Run standalone after planning finishes and before /start-roadmap.

2026-07-12180

critique-plan

ayoubben18/ab-method

Pre-implementation critic. Spins up a read-only domain critic that challenges a drafted plan — a task's missions or a roadmap's task graph — against the ubiquitous language, CONTEXT.md, and ADRs, and pushes back ONLY on genuine conflicts. Silent when the plan is sound. Use before implementing (from create-task / create-roadmap) or standalone to stress-test a plan against the project's domain model.

2026-07-11180

review-implementation

ayoubben18/ab-method

Post-implementation review. Spins up three read-only critics on a completed task's diff — cleaner-architecture, slop-defender, reusability-inspector — that push back ONLY on real issues. Autonomous runs apply safe fixes (tests-green-gated) and write everything to review.md next to progress-tracker.md; interactive runs present findings to pick. Use after a task's missions are done (from start-task / start-roadmap / create-task) or standalone on a diff.

2026-07-11180

ab-start-roadmap

ayoubben18/ab-method

Execute a roadmap autonomously to completion — the layer above start-task. Use when a roadmap's tasks are planned and you want them run in dependency order, with independent tasks optionally in parallel. Verifies the dependency tree is planned before running; stops if a needed task has no plan. Executor only.

2026-07-06180

ab-create-roadmap

ayoubben18/ab-method

Turn a larger idea into a dependency-ordered roadmap of tasks — the layer above create-task. Use when the work is several distinct tasks with real ordering between them (schema before API before UI), and you want the whole task graph drawn before implementing. Producer only; ab-start-roadmap executes it.

2026-07-05180