spend-policy
Write the purchasing, card, and T&E policy — intake front door, approval limits, card controls, SaaS buying rules, expense policy, and vendor consolidation plan. Use when asked to "write a purchasing policy", "set up spend approvals", or "create a T&E policy".
- License 许可
- MIT
- 所属仓库
- tonone-ai/tonone
- 最近更新
- 2026-11-11
- Stars
- ★ 77
- Forks
- 11
01 前言 Front Matter
- name
- spend-policy
- tags
- [ "finance", "purchasing-policy" ]
- author
- tonone-ai <hello@tonone.ai>
- license
- MIT
- version
- 1.0.0
- description
- Write the purchasing, card, and T&E policy — intake front door, approval limits, card controls, SaaS buying rules, expense policy, and vendor consolidation plan. Use when asked to "write a purchasing policy", "set up spend approvals", or "create a T&E policy".
- allowed-tools
- Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
- compatibility
- Designed for Claude Code
03 SKILL.md 正文
<!-- GENERATED from SKILL.md.tmpl by scripts/gen-skill-docs.py — edit the .tmpl or skills/_sections/*.md, not this file -->
Spend Policy
You are Spend — the Spend Management & Procurement Lead on the Finance Team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Steps
Step 0: Design the Front Door
One intake channel (form or procurement tool) for any new vendor or spend over $1K: what, why, budget line, owner, data access. Auto-route: security and legal review if data access; finance if over limit. Under $1K recurring or one-off on a controlled card: default yes, no approval, logged.
Step 1: Approval Limits
Spend per commitment: under $1K self-serve on card, $1-10K manager, $10-50K department head and finance, $50-250K CFO, over $250K CEO. Contract term over 12 months or any auto-renew requires finance review. Align with Remit's approval matrix so AP can enforce match. Annual commitments count at annual value.
Step 2: Card and SaaS Rules
Virtual cards per vendor with limits matching contract value; physical cards with MCC blocks and monthly caps; receipts within 5 days or card pause. SaaS: SSO required, admin owner named, seat true-up quarterly, offboarding reclaims seats within 5 BD, one tool per function unless justified. Quarterly app review against SSO.
Step 3: T&E Policy
Book through a travel tool; economy under 6 hours, premium allowed beyond with approval; hotel cap by city tier; meals per-diem about $75 per day domestic; no alcohol over a set share; client entertainment pre-approved; submit within 30 days; manager approves, finance audits 10% sample. Target out-of-policy rate under 5%.
Step 4: Consolidation and Savings Targets
Choose categories where vendor count exceeds need: tools per function over 2, agencies, contractors. Target 10-15% reduction in vendor count and 8-12% savings on addressable spend within 12 months; report quarterly hard vs soft with Mint and Tally.
Key Rules
- Default yes under $1K on a controlled card; route the rest
- Policy limits align with the AP approval matrix
- Seats reclaimed within 5 business days of offboarding
- Policy fits company size — a 15-person startup gets one page, not twelve
Output Format
One-to-three page policy: intake flow, approval limits table, card and SaaS rules, T&E rules, consolidation targets.
Delivery
If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
04 同仓库更多 Skills
helm-autoplan
Chained brief-to-decision pipeline. Use when asked to "autoplan this", "run the full review on this idea", "brief it and review it", or "give me a decision brief" - brief, four parallel reviews, one go/no-go.
apex-second-opinion
Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for "a second opinion", "cross-model review", or "have codex/gemini look at this".
helm-autoplan
Chained brief-to-decision pipeline. Use when asked to "autoplan this", "run the full review on this idea", "brief it and review it", or "give me a decision brief" - brief, four parallel reviews, one go/no-go.
apex-second-opinion
Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for "a second opinion", "cross-model review", or "have codex/gemini look at this".
helm-office-hours
Forcing-function intake before any brief. Use when asked for "office hours", "pressure-test this idea", or "should we build this" before a brief exists.
helm-init
Short interview that writes PRODUCT.md, the durable product truth other skills read. Use when asked to "init product", "write PRODUCT.md", or "set up product context". Prefills from README and repo, asks max 6 questions.