@v587d/capital-generation 2.10.2 → 2.11.0

package/selected-skills/financeskills/skills/retirement-planning/references/compound-growth.md

@@ -1,38 +0,0 @@
-# Compound Growth Guide
-
-## The Time Value of Money
-
-A dollar today is worth more than a dollar in the future because it can be invested and earn a return.
-
-**Future Value formula (lump sum):**
-`FV = PV × (1 + r)^n`
-
-**Future Value with regular contributions (monthly):**
-`FV = PV × (1 + r/12)^(12n) + PMT × [((1 + r/12)^(12n) − 1) / (r/12)]`
-
-where `r` = annual rate, `n` = years, `PMT` = monthly contribution.
-
-## Why Starting Early Matters
-
-| Start Age | Monthly Contribution | Balance at 65 (7%) |
-|---|---|---|
-| 25 | $300 | $906,000 |
-| 35 | $300 | $436,000 |
-| 45 | $300 | $189,000 |
-
-Starting at 25 vs. 35 yields more than double the outcome with the same contribution.
-
-## The Cost of Stopping Contributions
-
-Stopping contributions for just 5 years in your 30s costs more in lost growth than the contributions themselves, because early dollars have the longest compounding runway.
-
-## Inflation Adjustment
-
-To express a future sum in today's purchasing power:
-`Real FV = Nominal FV / (1 + inflation_rate)^n`
-
-At 2.5% inflation, $1M in 30 years has the purchasing power of ~$477,000 today.
-
-## Sources
-- Bogle, J. C. (2017). *The Little Book of Common Sense Investing*. Wiley.
-- Bernstein, W. (2010). *The Investor's Manifesto*. Wiley.

package/selected-skills/financeskills/skills/retirement-planning/references/retirement-fundamentals.md

@@ -1,29 +0,0 @@
-# Retirement Planning Fundamentals
-
-## How Much Do You Need? — The Nest Egg Target
-
-The most widely cited rule is the **4% Safe Withdrawal Rate** (Bengen, 1994):
-`Nest Egg = Desired Annual Income / 0.04`
-
-A $1.5M portfolio supports $60,000/year for at least 30 years with high historical probability (>95% success across US market history).
-
-**Conservative alternative**: Use 3.5% for a 40+ year horizon (FIRE movement standard).
-
-## Contribution Limits (US, 2024)
-| Account | Limit | Catch-Up (50+) |
-|---|---|---|
-| 401(k) / 403(b) | $23,000 | +$7,500 |
-| IRA (Traditional or Roth) | $7,000 | +$1,000 |
-| HSA (individual) | $4,150 | +$1,000 |
-| HSA (family) | $8,300 | +$1,000 |
-
-## Employer Match — Never Leave It on the Table
-An employer 4% match on a $80,000 salary = $3,200 free per year. This is a 100% instant return; always contribute at least enough to capture the full match.
-
-## Rule of 72
-A quick mental check: `Years to Double = 72 / Annual Return %`
-At 7% return, money doubles every ~10.3 years.
-
-## Sources
-- Bengen, W. P. (1994). Determining withdrawal rates using historical data. *Journal of Financial Planning*.
-- Pfau, W. (2018). *How Much Can I Spend in Retirement?* Retirement Researcher Media.

package/selected-skills/financeskills/skills/revenue-recognition/EXAMPLE.md

@@ -1,21 +0,0 @@
-# Worked Example - revenue-recognition
-
-## Ask
-
-> We sold a $12k annual subscription today. The customer paid upfront. How much revenue do we recognize this month?
-
-## What a correct response contains
-
-Should identify this as a multi-period performance obligation. Should calculate the monthly revenue ($1k). Should explain the deferral of the remaining $11k as Unearned Revenue. Should provide a Revenue Recognition Memo structure.
-
-## File-driven variant
-
-With fixture(s) `evals/files/contracts.csv`:
-
-> Contract C-101 in the attached file (evals/files/contracts.csv) was signed on 1 January for a fixed price of $100,000. Support and implementation are both delivered evenly over 12 months. Allocate the transaction price to each performance obligation using relative SSP per IFRS 15 / ASC 606, then compute revenue recognised by 31 March (3 months in). Show the allocation table and journal-ready amounts.
-
-Expected: Relative-SSP allocation: licence $60,000, support $24,000, implementation $16,000 (sums to $100,000). By 31 March: licence in full plus 3/12 of support and implementation = $70,000 recognised; $30,000 remains as contract liability.
-
-## Compute, don't estimate
-
-All figures above come from [`scripts/calculate.py`](./scripts/calculate.py) - import its functions rather than doing arithmetic in prose.

package/selected-skills/financeskills/skills/revenue-recognition/SKILL.md

@@ -1,86 +0,0 @@
----
-name: revenue-recognition
-description: When the user wants to apply complex revenue recognition rules (IFRS 15 / ASC 606). Also use when the user mentions "deferred revenue," "performance obligations," "contract assets," "multi-element arrangements," "SaaS revenue rules," or "unearned revenue."
-metadata:
-  version: 1.0.0
----
-
-# Revenue Recognition (IFRS 15 / ASC 606)
-
-You are a Technical Accounting Manager. Your goal is to ensure that revenue is recognized in a way that depicts the transfer of promised goods or services to customers.
-
-## Initial Assessment
-
-1. **Contract Analysis**
-   - Is there a formal contract?
-   - What are the distinct performance obligations? (e.g., Software license vs. Implementation vs. Support).
-
-2. **Transaction Price**
-   - Is there variable consideration (discounts, rebates, bonuses)?
-   - Is there a significant financing component?
-
-3. **Transfer of Control**
-   - Is revenue recognized "Point in Time" or "Over Time"?
-
----
-
-## Revenue Framework (The 5-Step Model)
-
-### Priority Order
-1. **Identify the Contract** (Existence and enforceability).
-2. **Identify Performance Obligations** (Are they distinct?).
-3. **Determine Transaction Price** (Expected value or most likely amount).
-4. **Allocate Transaction Price** (Based on Standalone Selling Price - SSP).
-5. **Recognize Revenue** (As control transfers).
-
----
-
-## Technical Accounting Steps
-
-### 1. Standalone Selling Price (SSP) Allocation
-- If a bundle is sold for $1,000, but the individual components (License + Support) are worth $800 and $400, allocate the $1,000 proportionally.
-
-### 2. Contract Assets vs. Receivables
-- Recognize a contract asset when the right to payment is conditional on something other than the passage of time.
-
-### 3. Deferred Revenue (Unearned)
-- Map the schedule for recognizing revenue over the life of a subscription or service period.
-
----
-
-## Output Format
-
-### Revenue Recognition Memo
-
-**The Contract**
-- Summary of performance obligations identified.
-- Transaction price determination.
-
-**Allocation Table**
-- Breakdown of how the price is spread across obligations.
-
-**Journal Entries**
-- Specific entries for Initial Recognition, Deferral, and monthly Amortization.
-
----
-
-## Scripts
-- [calculate.py](./scripts/calculate.py): Deterministic functions for this skill's core computations. Run `python3 scripts/calculate.py` to self-test; import the functions instead of doing mental math.
-
----
-
-## References
-- [IFRS 15 Summary](./references/ifrs15-guide.md): The official 5-step model details.
-- [SaaS Revenue Standards](./references/saas-rev-rec.md): Specifics for subscription businesses.
-
----
-
-## Assets
-- [allocation-workpaper-template.md](./assets/allocation-workpaper-template.md): 5-step IFRS 15 / ASC 606 workpaper.
-
----
-
-## Related Skills
-- **statement-preparation**: For accurately reporting revenue and deferred revenue.
-- **audit-checklist**: For auditing the revenue cycle.
-- **financial-analysis**: For analyzing the quality of earnings.

package/selected-skills/financeskills/skills/revenue-recognition/assets/allocation-workpaper-template.md

@@ -1,30 +0,0 @@
-# Revenue Recognition Workpaper (IFRS 15 / ASC 606)
-
-**Contract:** {id} | **Customer:** {name} | **Signed:** {date} | **Transaction price:** {amount}
-
-## Step 1-2: Contract & Performance Obligations
-| # | Performance obligation | Distinct? | Timing (PIT / over time) | Measure of progress |
-|---|---|---|---|---|
-
-## Step 3: Transaction Price
-Fixed: {x} | Variable (constrained): {x} | Financing component: {y/n} | Non-cash: {x}
-
-## Step 4: Allocation (relative SSP)
-| PO | SSP | SSP % | Allocated price |
-|---|---|---|---|
-| | | | |
-| **Total** | {ssp_total} | 100% | **{price - must tie}** |
-
-## Step 5: Recognition Schedule
-| PO | {p1} | {p2} | {p3} | {p4} | Total |
-|---|---|---|---|---|---|
-
-## Period-End Position
-Revenue recognised to date: {x} | Billed: {x} | Contract asset / (liability): {x}
-
-## Journal Entries
-| Date | Account | Dr | Cr |
-|---|---|---|---|
-
----
-*Allocation computed with scripts/calculate.py (allocate_transaction_price). AI-prepared - review required.*

package/selected-skills/financeskills/skills/revenue-recognition/references/ifrs15-guide.md

@@ -1,28 +0,0 @@
-# IFRS 15 / ASC 606: The Five-Step Model
-
-## Step 1 — Identify the Contract
-Criteria: approved, rights identifiable, payment terms identifiable, commercial substance, collection probable. Combine contracts entered near the same time with the same customer if negotiated as a package.
-
-## Step 2 — Identify Performance Obligations (POs)
-A promised good/service is distinct if: (a) customer can benefit from it alone or with readily available resources, AND (b) it is separately identifiable in the contract (not highly integrated, not significantly modifying another good/service).
-- Software + critical customization = often ONE PO.
-- Software + standalone support = TWO POs.
-
-## Step 3 — Determine Transaction Price
-- Variable consideration (rebates, penalties, usage tiers): estimate via expected value or most-likely amount, constrained so reversal is highly improbable.
-- Significant financing component if timing gap > 12 months.
-- Non-cash consideration at fair value.
-
-## Step 4 — Allocate to POs
-Pro-rata on standalone selling prices (SSP). SSP hierarchy: observable price → adjusted market assessment → expected cost plus margin → residual (restricted).
-
-## Step 5 — Recognize Revenue
-Over time if ANY: (a) customer simultaneously receives/consumes, (b) asset created/enhanced is customer-controlled, (c) no alternative use + enforceable right to payment for performance to date. Otherwise point in time (control transfer indicators: title, possession, risks/rewards, acceptance).
-
-## Contract Modifications
-- Adds distinct goods at SSP → separate contract.
-- Adds distinct goods NOT at SSP → prospective (terminate & replace).
-- Remaining goods not distinct → cumulative catch-up.
-
-## Disclosures
-Disaggregated revenue, contract balances (contract assets/liabilities), remaining performance obligations (backlog), significant judgments.

package/selected-skills/financeskills/skills/revenue-recognition/references/saas-rev-rec.md

@@ -1,26 +0,0 @@
-# SaaS Revenue Recognition Patterns
-
-## Typical POs in a SaaS Contract
-| Element | Distinct? | Pattern |
-|---|---|---|
-| Subscription/hosting | Yes (the core PO) | Ratable over term |
-| Implementation/setup | Usually NOT distinct if no standalone value | Roll into subscription, recognize over term (or over expected customer life if material) |
-| Premium support | Yes if sold separately | Ratable |
-| Usage/overage fees | Variable consideration | Recognize as usage occurs (royalty-style exception often applies) |
-| Professional services (config, training) | Often distinct | As delivered |
-
-## Key Judgments
-- **Setup fees**: Non-refundable upfront fees rarely transfer a distinct service → defer and amortize. Material renewal option advantage → amortize over expected life, not initial term.
-- **Term licenses + cloud**: On-prem license is point-in-time; SaaS is over-time. Hybrid deals need SSP allocation.
-- **Free trials/discounted first year**: Total contract price spread over total committed term.
-
-## Metrics Bridge (for finance reviews)
-- Billings = Revenue + ΔDeferred Revenue.
-- ARR ≠ revenue: ARR is contracted run-rate; revenue is recognized.
-- A growing gap between billings and revenue signals lengthening prepay terms, not necessarily growth.
-
-## Common Errors
-1. Recognizing setup fees on go-live (should be deferred).
-2. Straight-lining usage revenue (should follow actual usage).
-3. Ignoring material rights from renewal discounts.
-4. Commission costs (ASC 340-40 / IFRS 15 contract costs): capitalize and amortize over benefit period, including renewals if commissions on renewal aren't commensurate.

package/selected-skills/financeskills/skills/risk-assessment/EXAMPLE.md

@@ -1,21 +0,0 @@
-# Worked Example - risk-assessment
-
-## Ask
-
-> Our portfolio is 40% tech stocks and 60% crypto. What's the risk if the Fed raises interest rates?
-
-## What a correct response contains
-
-Should identify high interest rate sensitivity in tech and crypto. Should discuss the impact on the discount rate (valuing tech) and liquidity (crypto). Should suggest a VaR calculation or stress test. Should recommend diversification or hedging strategies.
-
-## File-driven variant
-
-With fixture(s) `evals/files/daily_returns.csv`:
-
-> Portfolio value $10,000,000. From the attached daily return history (evals/files/daily_returns.csv), compute 95% one-day historical VaR (in % and $), 95% parametric VaR assuming sigma=1.2% and zero mean, and annualized volatility. Compare the two VaR estimates.
-
-Expected: Historical VaR 1.94% ($194,370); parametric VaR $197,388; annualized vol 19.4%.
-
-## Compute, don't estimate
-
-All figures above come from [`scripts/calculate.py`](./scripts/calculate.py) - import its functions rather than doing arithmetic in prose.

package/selected-skills/financeskills/skills/risk-assessment/SKILL.md

@@ -1,83 +0,0 @@
----
-name: risk-assessment
-description: When the user wants to identify, quantify, and mitigate financial risks. Also use when the user mentions "market volatility," "credit risk," "liquidity gap," "stress testing," "Value at Risk," "VaR," "black swan events," or "what if the market crashes." Use this for portfolio management and enterprise risk.
-metadata:
-  version: 1.1.0
----
-
-# Risk Assessment
-
-You are a Risk Manager. Your goal is to identify potential threats to financial stability and recommend mitigation strategies to protect capital.
-
-## Initial Assessment
-
-1. **Risk Scope**
-   - Portfolio risk, Credit risk, or Operational risk?
-   - What is the time horizon (e.g., 1-day VaR, 1-year default risk)?
-
-2. **Data Requirements**
-   - Historical price volatility.
-   - Counterparty credit ratings.
-   - Current liquidity ratios.
-
----
-
-## Risk Framework
-
-### Priority Order
-1. **Identification** (What could go wrong?).
-2. **Quantification** (How likely is it and how much will it cost?).
-3. **Mitigation** (How can we lower the impact?).
-4. **Monitoring** (How do we track the risk over time?).
-
----
-
-## Technical Risk Steps
-
-### 1. Value at Risk (VaR)
-- Calculate VaR at 95% and 99% confidence levels using historical or parametric methods.
-- Explain the result: "There is a 5% chance the portfolio will lose more than $X in a single day."
-
-### 2. Stress Testing
-- Simulate "Black Swan" scenarios (e.g., interest rate spike, currency devaluation, sector-specific crash).
-
-### 3. Credit Risk Review
-- Evaluate the probability of default for key counterparties using Altman Z-Score or similar models.
-
----
-
-## Output Format
-
-### Risk Dashboard Structure
-
-**Executive Summary**
-- Top 3 Risk Exposures.
-- Risk Appetite Alignment (Within/Exceeding limits).
-
-**Quantitative Assessment**
-- VaR Analysis Table.
-- Stress Test Results (Scenario vs. Estimated Loss).
-- Concentration report (Are we too heavily invested in one area?).
-
-**Mitigation Plan**
-1. Hedging recommendations (Options, Swaps).
-2. Diversification steps.
-3. Liquidity reserve requirements.
-
----
-
-## Scripts
-- [calculate.py](./scripts/calculate.py): Deterministic functions for this skill's core computations. Run `python3 scripts/calculate.py` to self-test; import the functions instead of doing mental math.
-
----
-
-## References
-- [Risk Metrics Guide](./references/risk-metrics.md): Explaining VaR and Z-Score.
-- [Mitigation Strategies](./references/hedging-guide.md): Derivatives and diversification basics.
-
----
-
-## Related Skills
-- **investment-analysis**: To factor risk into the valuation.
-- **financial-analysis**: For detecting deteriorating liquidity signals.
-- **budget-forecast**: For building risk-adjusted financial plans.

package/selected-skills/financeskills/skills/risk-assessment/references/hedging-guide.md

@@ -1,24 +0,0 @@
-# Hedging Guide: Managing Financial Exposure
-
-Strategies for protecting an entity from adverse price movements in markets.
-
-## 🏛️ Common Hedging Instruments
-
-### 1. Options
-- **Put Options**: Protect against falling prices (downside protection).
-- **Call Options**: Protect against rising prices (for buyers of commodities).
-
-### 2. Futures & Forwards
-Contractual obligations to buy or sell an asset at a predetermined price on a future date. Used to lock in prices today.
-
-### 3. Swaps (Interest Rate Swaps)
-Exchanging floating-rate interest payments for fixed-rate payments to protect against rising interest rates.
-
----
-
-## 🔍 The Goal of Hedging
-The goal of hedging is **NOT** to make a profit. It is to **REDUCE UNCERTAINTY** and protect the core operations of the business from market volatility.
-
-## 🔗 Sources
-- [Investopedia: Hedging Definition](https://www.investopedia.com/terms/h/hedging.asp)
-- [CFI: Hedging Strategy](https://corporatefinanceinstitute.com/resources/knowledge/trading-investing/hedging-strategy/)

package/selected-skills/financeskills/skills/risk-assessment/references/risk-metrics.md

@@ -1,24 +0,0 @@
-# Risk Metrics: VaR & Z-Score
-
-Quantitative tools for measuring the probability and impact of financial failure.
-
-## 🏛️ Value at Risk (VaR)
-VaR measures the potential loss in value of a risky asset or portfolio over a defined period for a given confidence interval.
-
-### Interpretation
-"Our 1-day 95% VaR is $1M." 
-This means there is a **5% probability** that the portfolio will lose **more than $1M** in a single day.
-
----
-
-## 🔍 Altman Z-Score
-A formula used to predict the probability that a firm will go into bankruptcy within two years.
-
-### The Zones
-- **Z > 2.99**: "Safe" Zone.
-- **1.81 < Z < 2.99**: "Grey" Zone (Caution required).
-- **Z < 1.81**: "Distress" Zone (High probability of bankruptcy).
-
-## 🔗 Sources
-- [Investopedia: Value at Risk](https://www.investopedia.com/terms/v/var.asp)
-- [CFI: Altman's Z-Score Model](https://corporatefinanceinstitute.com/resources/knowledge/finance/altmans-z-score-model/)

package/selected-skills/financeskills/skills/sox-compliance/EXAMPLE.md

@@ -1,17 +0,0 @@
-# Worked Example - sox-compliance
-
-## Ask
-
-> I need to test a daily three-way-match control in P2P for the full year. Population is about 18,000 matched invoices. How many samples, how do I pick them, and what do I document?
-
-## What a correct response contains
-
-Sample of 25-40 (daily/per-transaction frequency), random selection across the full period including period-end, population completeness validation against the GL/system, and item-level attribute documentation.
-
-## File-driven variant
-
-With fixture(s) `evals/files/revenue_population.csv`:
-
-> This is the Jan-May population for the revenue approval control (evals/files/revenue_population.csv), which operates per-transaction (daily frequency). Determine the sample size per standard SOX guidance for a daily control, select the sample reproducibly (state your method/seed), test approval status across the FULL population programmatically, and classify any exceptions.
-
-Expected: Daily/multiple-times-daily control -> 25 selections (or 40 per some methodologies - state the table used). Programmatic scan of all 120 items finds 25 missing approvals -> exceptions to evaluate as deficiency; given the rate, classify at least significant-deficiency pending compensating controls and quantitative materiality.

package/selected-skills/financeskills/skills/sox-compliance/SKILL.md

@@ -1,88 +0,0 @@
----
-name: sox-compliance
-description: When the user wants to plan or execute SOX 404 control testing, select audit samples, build testing workpapers, or classify control deficiencies. Also use when the user mentions "SOX testing," "ICFR," "key controls," "sample selection," "test of design," "test of operating effectiveness," "significant deficiency," or "material weakness."
-metadata:
-  version: 1.0.0
----
-
-# SOX 404 Compliance Testing
-
-You are an Internal Controls Manager. Your goal is to test internal controls over financial reporting (ICFR) with defensible methodology: right scope, right samples, right documentation, right deficiency conclusions.
-
-## Initial Assessment
-
-1. **Scoping**
-   - Significant accounts and disclosures (quantitative materiality + qualitative risk).
-   - Mapped processes (revenue, P2P, payroll, close, ITGC) and their key controls.
-   - Control types: preventive/detective, manual/automated/IT-dependent manual.
-
-2. **Testing Context**
-   - Test of design (TOD) vs. test of operating effectiveness (TOE).
-   - Control frequency (drives sample size) and period covered.
-   - Reliance strategy: management testing vs. external auditor reliance.
-
----
-
-## Testing Framework
-
-### Sample Sizes by Control Frequency (standard practice)
-| Frequency | Population (annual) | Minimum Sample (TOE) |
-|---|---|---|
-| Annual | 1 | 1 |
-| Quarterly | 4 | 2 |
-| Monthly | 12 | 2–4 |
-| Weekly | 52 | 5–9 |
-| Daily | ~250 | 20–40 |
-| Multiple times daily / per transaction | >250 | 25–60 |
-Automated controls: test one instance per configuration + ITGC reliance (benchmarking permitted if ITGCs strong and no change).
-
-### Selection Method
-Random or haphazard WITHOUT bias; document the population source, completeness check of the population, and selection method. Cover the full period including period-end.
-
-### Deficiency Classification
-| Severity | Definition | Escalation |
-|---|---|---|
-| Control deficiency | Possible misstatement is inconsequential | Process owner remediation |
-| Significant deficiency | Less severe than MW but important enough to merit attention of those charged with governance | Audit committee reporting |
-| Material weakness | Reasonable possibility a MATERIAL misstatement would not be prevented/detected timely | Disclosure (ICFR opinion impact) |
-Evaluate: likelihood × magnitude, compensating controls, prudent-official test, aggregation with other deficiencies in the same account/assertion.
-
----
-
-## Technical Analysis Steps
-
-### 1. Test of Design
-Walk through one transaction end-to-end; assess whether the control, AS DESIGNED, addresses the risk/assertion (C, E/O, A, V, P&D).
-
-### 2. Test of Operating Effectiveness
-Execute the sample plan; for each item document: attribute tested, evidence inspected, performer, exception Y/N. One exception → expand sample or conclude deficiency (no "isolated exception" without root cause analysis and expanded testing).
-
-### 3. Deficiency Evaluation
-Root cause, magnitude (max exposure, not observed error), likelihood, compensating controls actually tested, aggregation. Conclude severity with rationale.
-
----
-
-## Output Format
-
-### SOX Testing Workpaper
-
-**Header**: Control ID, description, frequency, owner, assertion(s), period, tester, date.
-
-**Population & Sample**: source report, completeness validation, size, method, items listed.
-
-**Attributes & Results**: attribute matrix per sample item, exceptions detailed.
-
-**Conclusion**: Effective / Deficient + severity classification + remediation owner and deadline.
-
----
-
-## References
-- [Sampling Methodology](./references/sampling-methodology.md): Sample size rationale, expansion rules, and ITGC benchmarking conditions.
-
----
-
-## Related Skills
-- **audit-checklist**: For the broader (ISA/external) audit program beyond ICFR.
-- **risk-assessment**: For the risk assessment that drives SOX scoping.
-- **close-management**: Close process controls are perennial SOX scope.
-- **forensic-accounting**: When testing surfaces indicators of intentional override.

package/selected-skills/financeskills/skills/sox-compliance/references/sampling-methodology.md

@@ -1,27 +0,0 @@
-# SOX Sampling Methodology
-
-## Sample Size Logic
-Attribute sampling at 90% confidence, 0 expected deviations, ~10% tolerable rate yields ~22–25 items for large populations — the source of the common "25 for daily controls" convention. Lower-risk controls or strong ITGC environments justify the lower end of ranges; higher risk (new control, prior deficiency, management override exposure, period-end estimates) pushes to the upper end.
-
-## Risk-Tiering Adjustments
-| Factor | Effect on sample |
-|---|---|
-| Prior-year exception on this control | +50–100%, no benchmarking |
-| New/changed control or system | Test post-change period only, full sample within it |
-| High judgment/estimation control | Upper end + senior reviewer |
-| Strong, tested ITGCs + automated control | 1 per configuration; benchmark up to 2 future years if no change |
-
-## Exception Handling Protocol
-1. Confirm it's a true exception (not documentation gap — but chronic documentation gaps ARE control failures).
-2. Root cause with the control owner, in writing.
-3. Expand: common practice is to double the sample with zero further tolerance; any second exception → control concluded ineffective for the period.
-4. Never average away exceptions across periods; a mid-year remediation splits the testing period in two.
-
-## Population Completeness (the step that fails QA reviews)
-Before sampling, prove the population is complete: reconcile the report to the GL/system of record, validate report parameters (dates, entities, statuses), and for ITGC-dependent reports, confirm the report logic itself is tested (IPE — information produced by the entity).
-
-## Interim vs. Year-End (Rollforward)
-Interim testing (e.g., through Q3) requires rollforward procedures: inquiry + observation at minimum, re-testing for higher-risk controls, covering the stub period.
-
-## Documentation Minimum Per Sample Item
-Unique identifier, date, evidence examined (name the document), attribute-by-attribute pass/fail, tester initials/date. "No exceptions noted" without item-level detail is not evidence.

package/selected-skills/financeskills/skills/startup-valuation/EXAMPLE.md

@@ -1,21 +0,0 @@
-# Worked Example - startup-valuation
-
-## Ask
-
-> We have a SaaS startup with a working MVP and 2 technical co-founders. We're raising $500k. How much should we be valued at?
-
-## What a correct response contains
-
-Should apply the Berkus Method to assign value for 'Sound Idea', 'Prototype', and 'Quality Management'. Should ask about traction or TAM. Should provide a pre-money valuation range and suggest a stake for the $500k investment.
-
-## File-driven variant
-
-With fixture(s) `evals/files/round_terms.csv`:
-
-> Apply the VC method to the attached round terms (evals/files/round_terms.csv): compute post-money and pre-money valuation, the investor's required ownership, the implied IRR of a 10x-in-5-years target, and founder ownership after the round.
-
-Expected: Post-money $10,000,000; pre-money $8,000,000; investor ownership 20%; implied IRR 58.5%; founder falls to 48%.
-
-## Compute, don't estimate
-
-All figures above come from [`scripts/calculate.py`](./scripts/calculate.py) - import its functions rather than doing arithmetic in prose.

package/selected-skills/financeskills/skills/startup-valuation/SKILL.md

@@ -1,88 +0,0 @@
----
-name: startup-valuation
-description: When the user wants to value an early-stage company that may have little or no revenue. Also use when the user mentions "pre-seed valuation," "Berkus method," "VC method," "scorecard valuation," "valuing a startup," or "dilution modeling."
-metadata:
-  version: 1.0.0
----
-
-# Startup Valuation
-
-You are a Venture Capital Associate. Your goal is to determine a fair pre-money valuation for an early-stage entity using methodologies designed for high-uncertainty environments.
-
-## Initial Assessment
-
-1. **Stage & Traction**
-   - Is the company Pre-Seed, Seed, or Series A?
-   - Do they have a Minimum Viable Product (MVP)?
-   - What is the monthly growth rate of users/revenue?
-
-2. **The Team**
-   - Is there a technical co-founder?
-   - What is the previous exit experience of the founders?
-
-3. **Market Context**
-   - What is the Total Addressable Market (TAM)?
-   - What are the recent valuations of similar startups in this sector?
-
----
-
-## Valuation Framework
-
-### Priority Order
-1. **Qualitative Scoring** (Assessing the foundation via Berkus or Scorecard).
-2. **VC Method Calculation** (Working backwards from a target exit value).
-3. **Comparative Analysis** (Reviewing similar deals in the same stage/region).
-4. **Synthesis** (Determining the final pre-money valuation range).
-
----
-
-## Technical Valuation Steps
-
-### 1. Berkus Method Analysis
-Assign a value ($0 to $500k) for each of the following:
-- Sound Idea (Basic value).
-- Prototype (Reducing technology risk).
-- Quality Management Team (Reducing execution risk).
-- Strategic Relationships (Reducing market risk).
-- Product Rollout/Sales (Reducing production risk).
-
-### 2. VC Method (Exit-Oriented)
-1.  Estimate the **Exit Value** (based on comps at exit).
-2.  Identify the **Target Multiple of Money** (e.g., 10x).
-3.  Calculate the **Post-Money Valuation** (`Exit Value / Target Multiple`).
-4.  Subtract the **Investment Amount** to find the **Pre-Money Valuation**.
-
----
-
-## Output Format
-
-### Startup Valuation Memo Structure
-
-**Executive Summary**
-- Recommended Pre-Money Valuation.
-- Key strengths of the opportunity.
-
-**Methodology Breakdown**
-- **Berkus Scorecard**: Qualitative breakdown.
-- **VC Method**: Exit assumptions and math.
-
-**Deal Terms**
-- Suggested equity stake for the requested investment.
-- Post-money valuation.
-
----
-
-## Scripts
-- [calculate.py](./scripts/calculate.py): Deterministic functions for this skill's core computations. Run `python3 scripts/calculate.py` to self-test; import the functions instead of doing mental math.
-
----
-
-## References
-- [VC Method Guide](./references/vc-method.md): Deep dive into exit modeling.
-- [Berkus Method Origins](./references/berkus-method.md): Historical context and weighting.
-
----
-
-## Related Skills
-- **investment-analysis**: For valuing mature public companies.
-- **predictive-burn-rate**: To see if the valuation aligns with the company's capital needs.