Track and update action item status from natural language updates like 'Seanのメールには返信しておいた' or 'Lu対応予定'. Integrates with daily-comms-ops workflow. Use when managing action items across communication channels.
audit-control-designer
Generate audit-ready internal control design documents from As-Is business process inventories. Produces control IDs, assertion mappings, procedures, SoD analysis, KPIs, materiality thresholds, and implementation roadmaps. Use when building internal controls for new audit engagements, SOX/J-SOX compliance, or process improvement initiatives.
インストール方法を見る含まれるファイル(9)
- SKILL.md8.2 KB
- assets/control_design_template.md5.8 KB
- references/accounting_standards.md6.7 KB
- references/assertion_mapping.md6.3 KB
- references/control_templates.md13.6 KB
- references/kpi_catalog.md8.9 KB
- references/materiality_framework.md7.2 KB
- references/process_patterns.md10.1 KB
- references/sod_patterns.md9.4 KB
SKILL.md(原文)
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Audit Control Designer
Overview
This skill transforms As-Is business process inventories into comprehensive internal control design documents. It leverages generalized patterns from real audit engagements across industries (F&B, retail, manufacturing) to produce draft control designs that cover all five audit assertions, segregation of duties, KPIs, and implementation roadmaps.
When to Use
- Starting internal control design from an As-Is process inventory
- Building controls for a new audit engagement (SOX, J-SOX, PCAOB)
- Designing controls for a specific business domain (AP, Inventory, COGS, Returns)
- Reviewing and strengthening existing control frameworks
- Preparing for initial audit readiness assessment
Prerequisites
None. This is a knowledge-based skill that uses reference documents for pattern matching and generation.
Input Requirements
Required: As-Is Business Process Inventory
A table or list of business processes with at minimum:
- Process ID
- Process name/description
- Primary owner/department
- Frequency (daily, weekly, monthly)
- Current tools/records used
Optional: Context Variables
| Variable | Options | Default |
|---|---|---|
| Accounting Standard | US GAAP / IFRS / J-GAAP | US GAAP |
| Industry | F&B, Retail, Manufacturing, Services | General |
| Company Scale | Small (<50 employees), Medium (50-500), Large (500+) | Medium |
| System Environment | Paper+Excel, Partial ERP, Full ERP | Paper+Excel |
| Regulatory Context | SEC/SOX, J-SOX, Voluntary | SEC/SOX |
Workflow
Step 1: Confirm Context Variables
Ask the user to confirm or specify:
- Applicable accounting standard
- Industry and company scale
- Current system environment
- Regulatory requirements
If not specified, use defaults from the table above.
Step 2: Read As-Is Process Inventory
Read the user-provided process inventory. Identify:
- Total number of processes
- Business domains covered
- Frequency distribution (daily/weekly/monthly)
- Manual risk indicators
Step 3: Classify Processes into Business Patterns
Load references/process_patterns.md and classify each process into one or more patterns:
| Pattern | Domain | Key Processes |
|---|---|---|
| AP (Accounts Payable) | Invoice entry, reconciliation | Procurement, invoice processing, matching |
| Inventory | Stocktake, adjustments | Counting, valuation, shrinkage tracking |
| COGS Calculation | Cost computation | Period-end calculation, variance analysis |
| Returns/Credits | Return processing | Credit notes, period attribution, inventory adjustment |
| Price Management | Unit cost updates | Price revision, master data changes |
Step 4: Select Control Templates
Load references/control_templates.md and select applicable templates based on:
- Matched business patterns from Step 3
- Risk level of each process (High/Medium/Low from the process inventory)
- Audit assertions most at risk for each process (from pattern definitions)
Step 5: Verify Assertion Coverage
Load references/assertion_mapping.md and ensure all five assertions are covered:
- Completeness: All transactions recorded
- Accuracy: Amounts and quantities correct
- Valuation: Appropriate valuation methods applied
- Cut-Off: Correct period attribution
- Existence: Assets and transactions are real
Flag any assertion gaps and recommend additional controls.
Step 6: Perform SoD Analysis
Load references/sod_patterns.md and evaluate:
- Which duty pairs should be separated
- Current separation status (based on process ownership)
- Risk level (High/Medium/Low)
- Compensating controls for small organizations
Step 7: Select KPIs
Load references/kpi_catalog.md and assign KPIs to each control:
- Select relevant KPIs based on control objectives
- Define calculation methods
- Set baseline and target placeholders
- Identify data sources
Step 8: Set Materiality Thresholds
Load references/materiality_framework.md and define:
- Overall Materiality framework
- Performance Materiality (typically 50-75% of overall)
- Clearly Trivial threshold (typically 3-5% of overall)
- Control-specific thresholds
Step 9: Check Accounting Standards
Load references/accounting_standards.md and verify:
- Control design aligns with specified accounting standard
- Inventory valuation method is appropriate
- Revenue recognition rules are followed
- Any standard-specific requirements are addressed
Step 10: Generate Control Design Document
Use assets/control_design_template.md to produce the output containing:
- Overview: Scope, applicable standard, materiality
- Control Table: ID, type, objective, procedure, owner, frequency, evidence, remediation
- Assertion Mapping: Assertion x Control coverage matrix
- SoD Analysis: Duty pairs, risk, current state, recommendations
- KPI Definitions: KPI ID, name, formula, baseline, target
- Roadmap: Short-term (M+1 to M+4) and medium-term (M+6 to M+18) initiatives
- Open Questions: Items requiring confirmation or management decision
Output Format
The output follows the template in assets/control_design_template.md. Key sections:
- Control IDs follow the pattern:
C-[DOMAIN]-[NN](e.g., C-AP-01, C-INV-01) - Each control specifies: Type (Preventive/Detective), Assertion coverage, Procedure steps
- SoD pairs are rated High/Medium/Low risk
- KPIs include calculation formula and data source
- Roadmap uses M+N notation (months from project start)
- Open Questions are explicitly managed with options and recommendations
Customization Guidance
By Industry
- F&B: Emphasize inventory existence, waste tracking, portion control
- Retail: Emphasize shrinkage, POS reconciliation, returns processing
- Manufacturing: Emphasize WIP valuation, BOM accuracy, yield tracking
- Services: Emphasize revenue recognition, project costing, time tracking
By Scale
- Small: Accept compensating controls for SoD gaps, simplify procedures
- Medium: Full SoD where possible, standard procedures
- Large: Comprehensive SoD, automated controls, multi-level approval
By System Environment
- Paper+Excel: Focus on detective controls, manual evidence, version management
- Partial ERP: Hybrid controls, interface reconciliation
- Full ERP: Automated preventive controls, system-enforced SoD, audit trails
Resources
| Type | File | Purpose | When to Load |
|---|---|---|---|
| Reference | references/process_patterns.md | 5 business process patterns (AP, Inventory, COGS, Returns, Price) with industry variations | Step 3: Classify processes |
| Reference | references/control_templates.md | 8 control pattern templates (T-AP-01/02, T-INV-01/02, T-CO-01, T-VAL-01, T-CALC-01/02) | Step 4: Select templates |
| Reference | references/assertion_mapping.md | C/A/V/CO/E definitions, process-to-assertion mapping, coverage matrix template | Step 5: Verify assertion coverage |
| Reference | references/sod_patterns.md | 5 SoD pairs with risk ratings and compensating controls | Step 6: Perform SoD analysis |
| Reference | references/kpi_catalog.md | K01-K08 KPI definitions with formulas, baselines, and targets | Step 7: Select KPIs |
| Reference | references/materiality_framework.md | Overall/Performance/Trivial materiality, threshold guidelines, escalation rules | Step 8: Set materiality |
| Reference | references/accounting_standards.md | US GAAP/IFRS/J-GAAP differences affecting control design | Step 9: Check standards |
| Asset | assets/control_design_template.md | Output template with 7 sections + 2 appendices | Step 10: Generate output |
Integration with audit-doc-checker
After generating a control design document, run audit-doc-checker to validate quality:
- Generate control design with this skill
- Review with
audit-doc-checker(target score: 70+) - Address findings and regenerate affected sections
- Iterate until quality threshold is met
レビュー
まだレビューはありません。使ってみた感想をお寄せください。
同じリポジトリのスキル
概要と使いどころ
AI活用提案の専門コンサルタントスキル。LLM・AIエージェントの活用事例知識を基に、業界別、部門別、シーン別に最適なAI導入提案を行います。システム化、業務改善、効率化を得意とし、具体的な活用事例、期待効果、導入ステップを含む実践的な提案を提供します。Use when proposing AI/LLM adoption strategies for specific industries, departments, or business scenarios.
Generate AI-powered BPO service proposals for Japanese companies in the US market. Use when creating outsourcing proposals with AI service menus, ROI estimation, implementation roadmaps, and bilingual (JA/EN) proposal documents for 在米日系企業向けAI実装.
日本語の概要は準備中です。原文の説明を表示しています。
AI(LLM)が生成した日本語テキストの「AI臭」を検出・診断し、人間らしい文章にリライトするスキル。 Use when: 「AIっぽい文章を直して」「人間らしくリライトして」「AI臭を消して」「この文章をもっと自然にして」 「テキストのAI感を減らして」「機械っぽさを取りたい」 "make this sound more human", "remove AI tone", "humanize this text", "detect if this is AI-generated". 6つのAI特有パターン(視覚的マーカー、単調なリズム、マニュアル的構成、非コミット姿勢、抽象語の濫用、 定型メタファー)を正規表現ベースで検出し、0-100のAI臭スコアを算出。3つの人間化技法 (バランスを崩す・客観を崩す・論理を崩す)でリライトを実行する。 Note: 検出スクリプトは日本語テキスト専用。英語テキストの場合はClaude自身がreferences/を参照して分析・リライトする。
Review audit-related documents (control design documents, bottleneck analyses, requirements definitions, etc.) for quality, scoring them 0-100 with a severity-rated findings list. Use when reviewing audit documents, checking control design quality, or verifying cross-document consistency. Supports documents governed by US GAAP, IFRS, or J-GAAP.
日本語の概要は準備中です。原文の説明を表示しています。
AWS CLIの専門家スキル。EC2, S3, IAM, Lambda, RDS, ECS等の主要サービスのCLI操作を支援。IAMポリシー設計、クロスアカウント運用、セキュリティ設定、コスト最適化のベストプラクティスを提供。Use when working with AWS services via CLI, designing IAM policies, managing infrastructure, or automating cloud operations.