invoice-system

kazukinagata/shinkoku · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/kazukinagata/shinkoku --skill invoice-system
0 commentsdiscussion
summary

適格請求書等保存方式(インボイス制度)に関する包括的な知識ベース。

  • 制度の概要、記載要件、経過措置、仕入税額控除ルール、登録判断を支援する。
skill.md

インボイス制度(Invoice System)

適格請求書等保存方式(インボイス制度)に関する包括的な知識ベース。 制度の概要、記載要件、経過措置、仕入税額控除ルール、登録判断を支援する。

制度概要

インボイス制度(適格請求書等保存方式)は、令和5年(2023年)10月1日に開始された消費税の仕入税額控除に関する制度。課税事業者が仕入税額控除を受けるためには、原則として「適格請求書発行事業者」が発行する「適格請求書(インボイス)」の保存が必要となる。適格請求書発行事業者になるには税務署への登録申請が必要で、登録番号(T+13桁)が付与される。

令和8年度税制改正大綱(R7.12.26閣議決定)により、3割特例の新設、経過措置スケジュールの5段階化など大幅な変更がある。

クイックリファレンス

登録番号の形式

  • T + 13桁の数字
  • 法人: T + 法人番号(例: T1234567890123)
  • 個人: T + 固有番号(マイナンバーとは異なる)

適格請求書の6つの必須記載事項

  1. 発行事業者の氏名又は名称及び登録番号
  2. 取引年月日
  3. 取引内容(軽減税率対象品目の明示含む)
  4. 税率ごとに区分した対価の額及び適用税率
  5. 税率ごとに区分した消費税額等
  6. 受領者の氏名又は名称

現行の経過措置一覧(令和7年時点)

措置 内容 適用期限
2割特例 売上消費税額の20%を納付 R8.9.30を含む課税期間まで
免税事業者仕入控除 80%→70%→50%→30%→0% R11.10.1で完全移行
少額特例 税込1万円未満はインボイス不要 R11.9.30まで
少額返還インボイス免除 税込1万円未満は返還インボイス不要 恒久措置

消費税額の端数処理

  • 1インボイスにつき、税率ごとに1回の端数処理
  • 切捨て・切上げ・四捨五入いずれも可(事業者の選択)
  • 行ごとの端数処理は不可

リファレンスファイル参照ガイド

質問の内容に応じて、以下のリファレンスファイルを参照する:

質問カテゴリ 参照ファイル
適格請求書の記載事項・種類・端数処理 references/qualified-invoice-requirements.md
経過措置のスケジュール・控除率・期限 references/transitional-measures-timeline.md
仕入税額控除の要件・例外・保存ルール /tax-invoice-credit-context を実行する
登録すべきか・計算方法の選択 references/decision-flowchart.md
実務上のよくある間違い・注意点 references/common-pitfalls.md
登録申請・取消手続き・基準期間 references/registration-procedures.md
BtoC事業者の判断・価格戦略 references/btoc-and-pricing-strategy.md
その他の質問・特定状況 references/faq.md

回答パターン

ユーザーの質問に回答する際は、以下の構造に従う:

1. 結論(Answer)

質問に対する明確な回答を最初に提示する。

2. 根拠(Legal Basis)

関連する法令・通達を示す。例:

  • 「消費税法第57条の4に基づき、適格請求書の交付義務があります」
  • 「R8大綱により、R9年分から3割特例が新設されます(個人事業主のみ)」

3. 計算例(Calculation Example)

該当する場合は具体的な数値例を示す。金額は int(円単位の整数)で、端数処理ルール(CLAUDE.md 記載)に従う。

4. 注意点(Caveats)

  • 落とし穴や例外事項を指摘する
  • references/common-pitfalls.md の該当項目を参照

5. 免責事項(Disclaimer)

回答の末尾に以下を付記する:

この情報は一般的な税法の解釈に基づくものであり、個別の状況により異なる場合があります。具体的な判断は税理士等の専門家にご相談ください。

他スキルとのクロスリファレンス

関連スキル 用途 参照タイミング
consumption-tax 消費税の計算・申告書作成 消費税額の具体的な計算が必要な場合
journal 仕訳入力・帳簿管理 インボイスに基づく仕訳の記帳方法
reading-invoice 請求書画像のOCR読取 紙のインボイスをデータ化する場合
tax-advisor 税務全般のアドバイス インボイス以外の税務相談を含む場合
settlement 決算処理 消費税の経理処理を確認する場合

免責事項

  • 本スキルの情報は令和8年度税制改正大綱(令和7年12月26日閣議決定)までの内容を反映している
  • 国会での法案審議・成立により内容が変更される可能性がある(特に3割特例、5段階スケジュール)
  • 個別具体的な税務判断は、税理士等の専門家への相談を推奨する
  • インボイス制度の経過措置は年度ごとに適用条件が変わるため、適用年度を必ず確認すること
how to use invoice-system

How to use invoice-system on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add invoice-system
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/kazukinagata/shinkoku --skill invoice-system

The skills CLI fetches invoice-system from GitHub repository kazukinagata/shinkoku and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/invoice-system

Reload or restart Cursor to activate invoice-system. Access the skill through slash commands (e.g., /invoice-system) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.838 reviews
  • Aisha White· Dec 28, 2024

    Keeps context tight: invoice-system is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Advait Rao· Dec 20, 2024

    We added invoice-system from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Pratham Ware· Dec 16, 2024

    invoice-system is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Luis Khan· Dec 4, 2024

    Solid pick for teams standardizing on skills: invoice-system is focused, and the summary matches what you get after install.

  • Luis Torres· Nov 23, 2024

    invoice-system has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Nia Khanna· Nov 19, 2024

    I recommend invoice-system for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Michael Iyer· Nov 11, 2024

    Useful defaults in invoice-system — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Anaya Johnson· Nov 7, 2024

    invoice-system fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Hassan Martin· Oct 26, 2024

    invoice-system is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Tariq Yang· Oct 14, 2024

    Useful defaults in invoice-system — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

showing 1-10 of 38

1 / 4