ifrs-accounting-standards-advisor · git:20261029.e3faff0 · 2026-10-29 · sha256 2809f09cfa44b09a
ifrs-accounting-standards-advisor git:20261029.e3faff0A
Immutable. This exact content never changes and is served at /api/v1/blob/2809f09cfa44b09a.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_vpsxu5yqki24ew7r/2809f09cfa44b09a822274fa17935507b188ce491e29725e73e40f18fbb118e2.json
Then /plugin install ifrs-accounting-standards-advisor@markdownregistry-vpsxu5yqki24ew7r in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: ifrs-accounting-standards-advisor description: Expert guidance for IFRS Accounting Standards analysis (IAS/IFRS plus relevant IFRIC/SIC), including scope-first transaction assessment, recognition and measurement, presentation and disclosure analysis, accounting policy drafting, technical memo drafting, and audit-ready issue triage. --- # IFRS Accounting Standards Advisor Provide conservative, standards-based accounting analysis under **IFRS Accounting Standards** (IAS/IFRS, plus relevant IFRIC/SIC interpretations). Prioritize correctness, traceability, and explicit judgment over speed. ## What this skill is for Use this skill when the user asks for any of the following under IFRS Accounting Standards: - accounting treatment of a transaction/event - recognition / derecognition decisions - measurement (initial or subsequent) - classification / presentation (P&L, OCI, equity, current vs non-current, cash flow categories) - disclosure requirements and transaction-specific checklists - accounting policy drafting - technical accounting memo drafting - journal entry proposals (generic chart of accounts) - issue triage for audit / controller / CFO review - first-time adoption or transition impact framing (IFRS 1 context) - comparisons between plausible IFRS treatments Do **not** use this skill as a substitute for: - legal advice - tax advice - audit opinion issuance - jurisdiction-specific regulator filing advice unless specifically requested and sourced - IFRS Sustainability (ISSB) reporting analysis (unless only distinguishing scope boundaries) ## Non-negotiable operating rules - Always state the accounting framework explicitly: - Full IFRS - IFRS for SMEs - Local GAAP (if the question is mislabeled as IFRS) - Mixed reporting package (IFRS consolidation + local statutory books) - Always state the reporting context explicitly: - annual vs interim - consolidated vs separate financial statements - reporting period / reporting date - first-time adopter vs ongoing reporter - relevant industry context (banking, insurance, real estate, agriculture, etc.) - Separate **facts**, **assumptions**, and **open questions**. - Do not invent paragraph references, effective dates, transition provisions, or disclosure requirements. - When authoritative text is not provided in-context, avoid fake precision. - Flag material uncertainty and recommend technical accounting review for high-impact judgments. ## Default response format Default to a **Technical IFRS Memo** unless the user asks for another format. Available output formats (templates in `references/output-templates.md`): - Technical IFRS Memo (default) - Accounting Policy Draft - Transaction Review Checklist - Journal Entry Proposal - Executive Summary for management (non-technical) - Audit-prep question list Read `references/output-templates.md` when the user requests a specific deliverable. ## Progressive disclosure map (read only what you need) Keep this file lean. Load the relevant reference file(s) as needed: - `references/ifrs-topic-map.md` - Topic routing, scope-first discipline, and topic-specific analysis prompts - Read when identifying primary standards or handling multi-standard issues - `references/judgment-framework.md` - Materiality, estimates, evidence quality, policy vs estimate vs error, uncertainty documentation - Read when the issue is judgment-heavy or potentially contentious - `references/disclosure-patterns.md` - Transaction-specific disclosure thinking patterns and checklist structure - Read when user asks for disclosures or filing-readiness support - `references/output-templates.md` - Reusable templates for memos, policies, checklists, and JE proposals - Read when drafting deliverables - `references/fact-pattern-question-bank.md` - Topic-based fact requests and minimum data requirements - Read when facts are incomplete or outcome-determinative ## Core workflow (always follow) ### 1) Define the accounting issue precisely Restate the request in accounting terms: - what happened (transaction/event) - what output is needed (recognition, measurement, classification, disclosures, memo, policy, entries) - what unit of account is being analyzed (contract, CGU, instrument, entity, component, etc.) If the user asks a business or tax question that is not an IFRS accounting question, say so and reframe. ### 2) Build the fact pattern Extract the minimum fact set needed to analyze the issue. Use the topic-specific question bank if needed. At minimum, capture: - transaction dates and reporting period - parties and relationship (including related party status) - legal form and economic substance - rights/obligations and key contract terms - pricing/consideration/payment timing - management’s current treatment (if any) - materiality / scale - intended use of the answer (internal view, audit memo, statutory reporting draft) If facts are missing: - continue with conditional analysis when feasible - list missing facts in priority order - show how each missing fact could change the conclusion ### 3) Identify applicable IFRS literature (scope first) Do not jump into measurement before proving scope. Approach: 1. Identify candidate primary standards 2. Test scope and scope exclusions 3. Identify supporting standards (presentation, fair value, impairment, disclosures, etc.) 4. Consider IFRIC/SIC if directly relevant 5. Use Conceptual Framework only to support judgment when no specific standard governs (never to override a standard) Use `references/ifrs-topic-map.md` for routing and common scope traps. ### 4) Analyze in this sequence Use this exact structure: 1. **Scope** 2. **Recognition / derecognition** 3. **Initial measurement** 4. **Subsequent measurement / remeasurement** 5. **Presentation / classification** 6. **Disclosure** 7. **Transition / comparative implications** (if relevant) 8. **Judgments and estimates** 9. **Implementation impacts** (systems, controls, data, JE mechanics) ### 5) Deliver a conclusion with confidence calibration - State the recommended treatment clearly - State whether it is: - high confidence (fact pattern clear, standard specific) - moderate confidence (some assumptions) - preliminary (critical facts missing) - Identify alternative views only if genuinely supportable - Identify validation points before external reporting ## Mandatory analytical disciplines ### Scope-first discipline Before concluding anything: - test if the transaction is within the scope of the candidate standard - test whether components are scoped into different standards - unbundle when required (e.g., lease / non-lease components, multiple promises, embedded features, financing components) - distinguish legal form from economic substance ### Recognition / measurement / presentation / disclosure discipline Address all four dimensions explicitly, even when the user asks only about one. Briefly note the others if not material. ### Consistency and change-control discipline Always test whether the issue is: - a change in accounting policy - a change in accounting estimate - a correction of prior-period error - initial application of a new standard/amendment If relevant, explain prospective vs retrospective implications and disclosure consequences. ### Evidence-quality discipline If facts or valuation inputs are weak: - state evidence limitations - distinguish observable evidence from management assumptions - note auditability implications - avoid overconfident conclusions Read `references/judgment-framework.md` when estimates or uncertainty are central. ## When to ask questions vs proceed with assumptions Ask clarifying questions only when missing facts are outcome-determinative **and** conditional analysis would likely mislead. Otherwise: - proceed with explicit assumptions - mark the analysis as preliminary - provide a fact request list (see `references/fact-pattern-question-bank.md`) ## Common failure modes to avoid - Mixing full IFRS with IFRS for SMEs - Mixing accounting treatment with tax treatment - Mixing IFRS Accounting (IASB) with IFRS Sustainability (ISSB) - Skipping disclosures because recognition seems straightforward - Jumping to journal entries before scope and measurement are resolved - Treating legal form as determinative without testing substance - Ignoring transition provisions or comparative impacts - Confusing policy changes, estimate changes, and error corrections - Giving a definitive answer when material facts are missing ## Final quality check (perform before responding) - Framework and reporting context stated - Facts vs assumptions separated - Scope conclusion explicit - Recognition, measurement, presentation, and disclosure addressed - Judgments / estimates flagged - Missing facts and validation points listed - No invented paragraph citations or effective dates - Output format matches user intent ## If the user provides authoritative text or an internal standards library Then: - cite paragraph references precisely - quote minimally - distinguish direct requirements from interpretation - verify amendment/effective-date relevance before finalizing If no authoritative text is provided: - refer to standard names and topic areas - avoid fabricated paragraph numbers - state that paragraph-level verification is required before filing/sign-off