agentic-council

Use when orchestrating monthly or quarterly close. Covers the close calendar, sub-ledger cutoffs, accruals, reclass entries, and post-close review. Do not use for individual reconciliations (use finance-reconciliation) or journal-entry construction (use finance-journal-entries).

Use when testing a SOX 404 control or designing a controls walkthrough. Covers control description, design effectiveness, operating effectiveness, deficiency evaluation, and remediation. Do not use for evidence-package preparation (use finance-evidence-package — Phase 3+).

Use when constructing a GAAP/IFRS journal entry from facts. Covers debit/credit selection, account coding, sub-ledger impact, and supporting memo. Do not use for reconciliation (use finance-reconciliation) or close orchestration (use finance-close-checklist).

Use when reconciling a balance-sheet account during the close cycle. Covers sub-ledger to GL ties, intercompany eliminations, exception triage, and audit-ready documentation. Do not use for journal-entry construction (use finance-journal-entries) or close orchestration (use finance-close-checklist).

Use when answering a federal, state, or international tax question that requires authoritative research. Covers IRC, Treasury Regs, Rev Rul/Proc, case law, and applicable treaty positions. Do not use for tax-provision computation (use finance-provision — Phase 3+).

Use when explaining actual-vs-plan or actual-vs-prior variance with commentary. Covers volume/price/mix decomposition, run-rate impact, and management commentary. Do not use for forecast revision (use finance-forecast-update — Phase 3+) or close orchestration (use finance-close-checklist).

Use when designing component interaction specs with visual states, transitions, and accessibility requirements. Covers state matrices, responsive behavior, ARIA compliance, and content constraints. Do not use for multi-step user journey mapping (use journey-mapping).

Use when mapping complete user journeys through multi-step flows, onboarding sequences, or feature workflows. Covers entry points, happy paths, alternate paths, error states, friction analysis, and delight opportunities. Do not use for individual component interaction specs (use interaction-design).

Use when analyzing an existing codebase for architecture, tech stack, conventions, and infrastructure. Covers project structure mapping, data model discovery, integration point cataloging, and constraint identification. Do not use for schema changes (use schema-design) or API contract definition (use api-design).

Use when designing documentation architecture for a project or team. Covers audience mapping, Diataxis framework classification, onboarding path design, format and location decisions, documentation testing, and maintenance scheduling. Do not use for recording individual architecture decisions (use adr-template) or creating versioned changelogs (use changelog-design).

Use when auditing codebase patterns or evaluating proposed changes for convention consistency. Covers file naming, component patterns, data fetching, state management, and type conventions. Do not use for test plan design or coverage targets (use testing-strategy).

Use when classifying data elements by sensitivity tier and defining per-tier handling requirements. Covers data inventory, sensitivity classification, PII flow mapping, encryption and masking specifications, and cross-boundary transfer documentation. Do not use for regulatory gap analysis (use compliance-review) or audit logging design (use audit-trail-design).

Use when modeling infrastructure costs, projecting scaling expenses, or identifying optimization opportunities across cloud providers and third-party services. Covers per-unit cost estimation, growth milestone projections, and budget alerting setup. Do not use for deployment strategy design (use deployment-plan) or monitoring architecture (use observability-design).

Use when designing an evaluation framework for AI/LLM features. Covers golden dataset creation, automated scoring rubrics, hallucination detection, regression testing infrastructure, and production monitoring. Do not use for prompt design (use prompt-engineering) or RAG pipeline architecture (use rag-architecture).

Use when designing, evaluating, or versioning system prompts for LLM-powered features. Covers instruction structure, chain-of-thought patterns, output format constraints, few-shot example selection, and prompt versioning strategy. Do not use for RAG pipeline design (use rag-architecture) or AI evaluation frameworks (use ai-evaluation).

Use when designing features that exist in competing products or analyzing prior art in the market. Covers feature mapping, UX evaluation, technical trade-off assessment, and differentiation opportunity identification. Do not use for evaluating individual libraries (use library-evaluation) or assessing technology maturity (use technology-radar).

Use when evaluating frameworks, tools, or platforms for adoption, migration, or stack decisions. Covers maturity assessment, ecosystem health, team readiness, migration cost, and long-term viability with radar quadrant placement. Do not use for comparing individual libraries (use library-evaluation) or analyzing competing products (use competitive-analysis).

Use when systematically identifying failure scenarios for proposed features and infrastructure changes. Covers component enumeration, failure mode discovery, cascade analysis, mitigation design, monitoring signals, and rollback planning. Do not use for security threat modeling (use threat-model) or input boundary testing (use edge-case-enumeration).

Use when applying STRIDE threat modeling to identify security risks in proposed features. Covers trust boundary mapping, data flow analysis, threat rating, mitigation proposals, and residual risk documentation. Do not use for failure scenario discovery (use failure-mode-analysis) or boundary value testing (use edge-case-enumeration).

Use when comparing multiple features or initiatives to determine prioritization order. Covers RICE scoring with quantified reach, impact, confidence, and effort dimensions, tier ranking, and success metric definition. Do not use for MVP scope definition (use mvp-scoping) or analytics instrumentation planning (use analytics-design).

Use when defining minimum viable scope for a product or feature launch. Covers MoSCoW prioritization, value-effort matrix analysis, MVP cut-line definition, and phased roadmap planning. Do not use for quantified feature comparison (use impact-estimation) or measurement instrumentation (use analytics-design).