Set up and manage NotebookLM notebooks for IT consulting engagements. Use this skill when the user asks to "set up a notebook for an RFP", "RFPのノートブックを 作成", "upload RFP to NotebookLM", "RFP資料をアップロード", "extract requirements from the RFP", "要件を抽出", "create engagement notebook", "案件ノートブック作成", "add amendment to notebook", "追加資料をノートブックに追加", "which notebook has the RFP", "RFPはどのノートブックにありますか", "prepare notebook for proposal", "提案準備のノートブック設定", "run RFP extraction", "RFP分析を実行", "briefing from RFP", "RFPブリーフィング作成", or any request to create, manage, or query NotebookLM notebooks for consulting engagements. Also trigger for "notebooklm setup", "notebook管理", "source management", "ソース管理", and requests to produce a structured RFP brief from uploaded documents.
Create IT consulting proposals and quotation documents grounded in customer RFP/RFQ uploaded to NotebookLM. Use this skill whenever the user asks to "create a proposal", "write a proposal", "draft a quotation", "make a bid", "prepare an RFP response", "提案書を作成", or needs to produce a formal consulting proposal for software development, infrastructure, or digital transformation projects. Also trigger when the user mentions "proposal", "quotation", "見積書", "提案", or wants to put together a client-facing project offer document — even if they don't say "proposal" explicitly.
Manage formal scope change requests for IT consulting projects following Japanese SIer change management conventions. Use this skill when the user asks to "create a change request", "変更管理", "スコープ変更", "scope change", "change order", "CR作成", "変更依頼書を作成", "impact analysis for a change", "変更影響分析", "assess scope change impact", or needs to formally document, evaluate, and track project changes against the original RFP baseline. Also trigger for "追加要件", "仕様変更", "additional requirements", "change control board", "CCB", and any request to manage scope creep or formal change processes.
Create cost estimations, budget breakdowns, and pricing for IT consulting projects, grounded in customer RFP/RFQ from NotebookLM. Use this skill when the user asks to "estimate cost", "create a budget", "calculate pricing", "費用見積", "コスト計算", "how much will this cost", "rate card", "TCO analysis", "total cost of ownership", or needs to produce financial projections for a project proposal. Also trigger for "予算", "単価", "pricing model", and any request involving project financials, billing structure, or cost-benefit analysis.
Create visually polished proposal presentations using Claude Design with Japanese enterprise design conventions. Use this skill when the user asks to "design the presentation in Claude Design", "Claude Designでプレゼン作成", "create a visual presentation", "ビジュアルプレゼン", "design beautiful slides", "make the presentation look professional", "polish the proposal deck", "デザインプレゼン", or wants to leverage Claude Design for high-quality visual presentation output. Also trigger for "Claude Design presentation", "visual deck", "デザイン提案資料", and any request that specifically mentions Claude Design for presentation work. This skill complements proposal-presentation — use proposal-presentation for content structure and Q&A prep, then this skill for visual polish via Claude Design.
Estimate project effort using WBS, function points, or story points, grounded in customer RFP/RFQ from NotebookLM. Use this skill when the user asks to "estimate effort", "create a WBS", "how long will this take", "工数見積", "work breakdown", "man-month estimate", "story point estimation", "estimate timeline", "how many man-months", or needs to break down a project into tasks with duration estimates. Also trigger for "見積もり", "FP法", "function point", "COCOMO", and any request to estimate development time or resources.
Conduct structured post-project reviews and generate lessons learned documents for IT consulting engagements. Use this skill when the user asks to "create a lessons learned report", "案件振り返り", "project retrospective", "post-mortem", "振り返り会", "KPT analysis", "what went well / what didn't", "プロジェクト完了報告", "project close-out report", or needs to formally review project outcomes against original plans. Also trigger for "反省会", "改善提案", "ふりかえり", "planned vs actual analysis", and any request to capture and document project learnings for organizational improvement.
Create post-delivery maintenance and support contract proposals for IT systems. Use this skill when the user asks to "create a maintenance proposal", "保守運用提案", "support contract proposal", "SLA definition", "SLA定義", "maintenance plan", "保守計画", "運用設計", "operations proposal", "post-go-live support", "create a support plan", or needs to propose ongoing maintenance, monitoring, and support services after project delivery. Also trigger for "保守見積", "年間保守", "ヘルプデスク提案", "incident management plan", and any request to define post-delivery support structures, SLAs, or maintenance pricing.