「document」の検索結果

Conduct a defensible cybersecurity risk assessment using the NIST SP 800-30 Rev 1 methodology: prepare scope and a risk model, identify threat sources and threat events, identify vulnerabilities and predisposing conditions, determine likelihood and impact, compute risk, and communicate results as a prioritized risk register. Use when an organization needs an actual risk *assessment* (not a maturity score), when a control framework (CSF, ISO 27001, RMF, SOC 2, PCI) requires a documented risk analysis as input, when leadership asks "what are our top risks and how bad are they", when assessing risk for a new system or major change, or when building a risk register from scratch. This is the methodology that feeds framework selection, ATO packages, and treatment decisions. Keywords: risk assessment, NIST 800-30, threat modeling, likelihood and impact, risk register, risk analysis, threat sources, vulnerabilities, risk determination, qualitative risk, risk matrix, residual risk, risk treatment.

日本語の概要は準備中です。原文の説明を表示しています。

Build comprehensive threat actor profiles using open-source intelligence (OSINT) techniques to document adversary motivations, capabilities, infrastructure, and TTPs for proactive defense.

日本語の概要は準備中です。原文の説明を表示しています。

Build a vulnerability exception and risk acceptance tracking system with approval workflows, compensating controls documentation, and expiration management.

日本語の概要は準備中です。原文の説明を表示しています。

Build collaborative forensic incident timelines using Timesketch to ingest, normalize, and analyze multi-source event data for attack chain reconstruction and investigation documentation.

日本語の概要は準備中です。原文の説明を表示しています。

Perform static analysis of malicious PDF documents using peepdf, pdfid, and pdf-parser to extract embedded JavaScript, shellcode, and suspicious objects.

日本語の概要は準備中です。原文の説明を表示しています。

Synchronize project documentation with recent code changes, refactors, and feature implementations in the current branch.

日本語の概要は準備中です。原文の説明を表示しています。

Build and create a git commit following this repository's established message format. Use when the user asks to "commit", "commit all changes", "commit and document", or similar. Also applicable when any agent (gemini-cli, codex, qwen, opencode, claude-code) needs to stage and commit a set of changes with a properly structured message.

日本語の概要は準備中です。原文の説明を表示しています。

Use when user asks to "build a Solana dapp", "write an Anchor program", "create a token", "debug Solana errors", "set up wallet connection", "test my Solana program", "deploy to devnet", or "explain Solana concepts" (rent, accounts, PDAs, CPIs, etc.). End-to-end Solana development playbook covering wallet connection, Anchor/Pinocchio programs, Codama client generation, LiteSVM/Mollusk/Surfpool testing, and security checklists. Integrates with the Solana MCP server for live documentation search. Prefers framework-kit (@solana/client + @solana/react-hooks) for UI, wallet-standard-first connection (incl. ConnectorKit), @solana/kit for client/RPC code, and @solana/web3-compat for legacy boundaries.

日本語の概要は準備中です。原文の説明を表示しています。

AI agent integration layer for the Pump SDK — agent instruction files, .well-known discovery, LLM context documents, 15+ skill files, MCP server prompts, and terminal management rules for GitHub Copilot and Gemini.

日本語の概要は準備中です。原文の説明を表示しています。

Audit the project's documentation (CLAUDE.md, .claude/rules, skills, README, CONTRIBUTING, SECURITY, .env.example, app/data/*.md, learn articles) against the actual code and config, and fix drift. Use after refactors, dependency or workflow changes, or on a schedule.

日本語の概要は準備中です。原文の説明を表示しています。

Write substantial agent-consumed guidance such as skills, AGENTS.md instructions, and documents reached by agent context pointers. Do not use for ordinary README or user-facing prose.

日本語の概要は準備中です。原文の説明を表示しています。

This skill should be used when creating RFQ (Request for Quotation) documents for software development projects to send to vendors. Use this skill when you have received vague requirements from clients and need to structure them into clear, comprehensive RFQs that enable vendors to provide accurate estimates. Supports Japanese (default) and English, with systematic requirements elicitation, clarification, and markdown-formatted output.

日本語の概要は準備中です。原文の説明を表示しています。

This skill should be used when creating UAT (User Acceptance Testing) test cases in Excel format for Salesforce CRM projects. It generates standardized test case documents with summary sheets and detailed test case lists, following a specific format structure with test case ID, priority, category, scenario, preconditions, test steps, expected results, and acceptance criteria.

日本語の概要は準備中です。原文の説明を表示しています。

This skill should be used when creating cost estimates and quotations for software development projects. Use this skill when you have an RFQ (Request for Quotation), project requirements, or a project description and need to create a comprehensive estimate with WBS, effort calculations, cost breakdowns, and ROI analysis. Supports Japanese (default) and English, with systematic work breakdown, effort estimation, and markdown-formatted estimate documents.

日本語の概要は準備中です。原文の説明を表示しています。

Format documents for Japanese enterprise approval workflows including ringi (稟議), purchase requests (購入申請), and internal proposals. Handles bilingual requirements, proper keigo levels, required approval sections, and corporate template compliance.

日本語の概要は準備中です。原文の説明を表示しています。

Professional project management skill aligned with PMBOK® 6th/7th Edition standards. Use this skill when you need to define requirements (ISO/IEC/IEEE 29148), review project plans, generate progress reports with Earned Value Management (EVM), conduct risk analysis, estimate costs, or provide project health assessments. Ideal for creating comprehensive project documentation, analyzing project performance metrics (SPI, CPI, EAC), managing risks across 14 categories, and ensuring stakeholder alignment. Triggers: "create project plan", "analyze project health", "calculate EVM", "risk assessment", "requirements definition", "progress report", "cost estimation", or requests involving PMBOK knowledge areas.

日本語の概要は準備中です。原文の説明を表示しています。

Cross-reference project artifacts (WBS, meeting minutes, requirements docs) by date, participant, and action items. Extract commitments from meeting minutes and link to WBS tasks. Generate traceability reports showing which decisions were captured in which documents.

日本語の概要は準備中です。原文の説明を表示しています。

Prepare comprehensive meeting assets including agendas, reference materials, decision logs, and action items. Use when user says "prepare meeting", "create agenda", "meeting prep", "会議準備", or needs bilingual (Japanese/English) meeting documentation for cross-regional teams. Triggers include requests for decision log templates, action item tracking, or compiling reference materials from project estimates and specs.

日本語の概要は準備中です。原文の説明を表示しています。

Generate formal IT/hardware purchase request documents from informal requirements. Use when creating purchase justifications, cost-benefit analyses, ROI calculations, vendor comparisons, or MARP presentation slides for management approval.

日本語の概要は準備中です。原文の説明を表示しています。

This skill should be used when creating professional presentation materials, slide decks, or proposal documents following FUJISOFT America's corporate template standards. Triggers include requests like "create a presentation", "make slides", "prepare proposal materials", "FUJISOFT template", or when MARP-format Markdown presentations are needed with consistent corporate branding. The skill provides a complete MARP template with CSS styling, visual design components, and quality assurance workflows.

日本語の概要は準備中です。原文の説明を表示しています。

Transform client hearing sheets and meeting notes into structured requirements documents. Use when converting raw hearing data (Japanese/English) into formal requirements, generating traceability matrices, identifying gaps/ambiguities, and mapping requirements to WBS items. Triggers include "hearing to requirements", "meeting notes to specs", "requirements traceability", "gap analysis for requirements", or requests involving hearing sheet analysis.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill for critical code review that focuses on whether the code actually works correctly and achieves the expected results - not just whether it matches a design document. This skill assumes designs can be wrong, finds bugs the design didn't anticipate, and verifies end-to-end correctness. Triggers include "critical code review", "deep code review", "verify this implementation works", "find bugs in this code", or reviewing implementation against requirements. NOTE - Security review is OUT OF SCOPE; use a dedicated security review skill for that purpose.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill when creating executive-level briefing materials, board reports, management meeting presentations, or investor briefings. This skill provides the "So What? / Why Now? / What Next?" framework, data visualization guidelines optimized for executives, and professional templates for rapid document creation. Triggers include "create board report", "executive summary", "management meeting materials", "investor presentation", "one-page summary", or requests to communicate complex information to senior leadership.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。