// Analyze and document a project's backend patterns — API design, data access, service structure. Use when the user wants a backend-only architecture analysis.
Resume a handoff (a side-topic spun off mid-grill) and turn it into a test-driven task. Use when the user wants to continue grilling on a deferred topic captured under docs/handoffs/.
Compact the current conversation (or a side-topic that surfaced mid-grill) into a handoff document another agent can pick up. Use when a tangent deserves its own task, or to summarize a session for a fresh agent.
Extend an existing goal — broaden or add to its objective, building on top of what the earlier /goal run already implemented. Use when the user wants to expand a goal after a /goal run.
Analyze and document a project's frontend patterns — component structure, state management, conventions. Use when the user wants a frontend-only architecture analysis.
Analyze a project's architecture end to end — extract domain language, map the tech stack, document frontend and backend patterns. Use when onboarding a new codebase or refreshing the architecture baseline.
Produce a ready-to-run prompt for an autonomous /goal loop. Use when the user wants to hand off one continuous objective with a verifiable stop condition to run autonomously.
| name | ab-analyze-backend |
| description | Analyze and document a project's backend patterns — API design, data access, service structure. Use when the user wants a backend-only architecture analysis. |
This skill runs the AB Method analyze-backend workflow.
Follow the workflow defined in .ab-method/core/analyze-backend.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.