「gap」の検索結果

Perform a Computer Systems Validation (CSV) assessment following GAMP 5 methodology. Covers user requirements, risk assessment, IQ/OQ/PQ planning, traceability matrix creation, and validation summary reporting. Use when a new computerized system is being introduced in a GxP environment, when an existing validated system is undergoing significant change, when periodic revalidation is required, or when a regulatory inspection demands a validation gap analysis.

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

Log a bias-log / vipassana observation to the memex store the moment a reasoning pattern surfaces, mid-session or at close. Use when you catch a bias in your own reasoning (anchoring, confirmation, trust-the-summary), when a pace tell or verification gap appears, or when meditate/observe produces a reflection worth persisting across sessions. Primary path pipes the body to `memex add` over stdin (`--title` required) then runs the `meditate-vipassana` extractor to make it queryable; secondary path appends a numbered bullet to `docs/OBSERVATIONS.md`.

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

Guide a person through structured learning of a new topic, technology, or skill. AI acts as learning coach — assessing current knowledge, designing a learning path, walking through material, testing understanding, adapting difficulty, and planning review sessions for retention. Use when a person wants to learn a new technology and does not know where to start, when someone feels overwhelmed by documentation, when a person keeps forgetting material and needs spaced repetition, or when transitioning between domains and needing a gap analysis.

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

Implement electronic signatures compliant with 21 CFR Part 11 Subpart C and EU Annex 11. Covers signature manifestation (signer, date/time, meaning), signature-to-record binding, biometric vs non-biometric controls, policy creation, and user certification requirements. Use when a computerized system requires legally binding electronic signatures for GxP records, when replacing wet-ink signatures in regulated workflows, when implementing batch release or document approval workflows, or when a regulatory gap reveals missing signature controls.

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

Epistemic transparency — acknowledging uncertainty, flagging limitations, avoiding overconfidence, and communicating what is known, unknown, and uncertain with proportional confidence. Maps the HEXACO personality dimension to AI reasoning: truthful calibration of confidence, proactive disclosure of gaps, and resistance to the temptation to appear more certain than warranted. Use before presenting a conclusion, when answering questions where knowledge is partial or inferred, after noticing a temptation to state uncertain information as certain, or when a user is making decisions based on provided information.

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

Evolve an existing agent definition by refining its persona in-place or creating an advanced variant. Covers assessing the current agent against best practices, gathering evolution requirements, choosing scope (refinement vs. variant), applying changes to skills, tools, capabilities, and limitations, updating version metadata, and synchronizing the registry and cross-references. Use when an agent's skills list is outdated, user feedback reveals capability gaps, tool requirements have changed, an advanced variant is needed alongside the original, or the agent's scope needs sharpening after real-world use.

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

Build and maintain a library collection through acquisitions, weeding (deaccessioning), collection assessment, reader advisory, and interlibrary loan coordination. Covers selection criteria, collection development policies, the CREW/MUSTIE method for weeding, usage analysis, and responsive collection management. Use when building a new collection with a defined scope and budget, assessing an existing collection for gaps or outdated materials, when shelves are overcrowded and systematic weeding is needed, or when establishing a formal collection development policy.

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

Design a compliance architecture that maps applicable regulations to computerized systems. Covers system inventory, criticality classification (GxP-critical, GxP-supporting, non-GxP), GAMP 5 category assignment, regulatory requirements traceability, and governance structure definition. Use when establishing a new regulated facility, formalising compliance across multiple systems, addressing a regulatory gap analysis, harmonising compliance after mergers or reorganisations, or preparing a site master file that references computerized systems.

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

Evolve an existing skill by refining its content in-place or creating an advanced variant. Covers assessing the current skill, gathering evolution requirements, choosing scope (refinement vs. variant), applying changes, updating version metadata, and synchronizing the registry and cross-references. Use when a skill's procedure steps are outdated, user feedback reveals gaps, a skill needs a complexity upgrade, an advanced variant is needed alongside the original, or related skills are added and cross-references are stale.

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

Evolve an existing team composition by refining its structure in-place or creating a specialized variant. Covers assessing the current team against template and coordination patterns, gathering evolution requirements, choosing scope (adjust members, change coordination pattern, split/merge teams), applying changes to the team file and CONFIG block, updating version metadata, and synchronizing the registry and cross-references. Use when a team's member roster is outdated, coordination pattern no longer fits, user feedback reveals workflow gaps, a specialized variant is needed alongside the original, or agents have been added or removed from the library affecting team composition.

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

Read-only audit of a GitHub repository's security posture. Gathers ref protection (rulesets AND classic branch protection), Actions token permissions, code and supply-chain features (Dependabot, secret scanning, push protection, CodeQL), and repo hygiene toggles via `gh api`, then classifies findings against essential / recommended / advanced tiers into a PASS/GAP report. Makes NO changes. Use when reviewing a repo before open-sourcing or a release, auditing a public user-owned repo whose CI auto-commits to the default branch, verifying a hardening change actually took effect, or producing a baseline security posture report for a repository.

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

Audit and repair Claude Code discovery symlinks for skills, agents, and teams. Compares registries against .claude/ directories at project and global levels, detects missing, broken, and extraneous symlinks, distinguishes almanac content from external projects, and optionally repairs gaps. Use after adding new skills or agents, after a repository rename or move, when slash commands stop working, or as a periodic health check.

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

Use when a concept needs practising: the user asks for an exercise, quiz, recall, or gap probe. Not for explanations: use explain-concept.

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

Use when the user and agent may hold different pictures of current state after a gap, sync request, or exposed stale claim. Not for persistence: use memory-update.

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

Use when the human returns after a gap, cannot follow the project, asks what happened, or wants a visual HTML recap page. Not for onboarding: use onboard. Not for handoff: use handoff.

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

Use when a landed merge, release, or completed change needs its cleanup surface reconciled. Scans for stale TODOs, deprecations, unused flags, and doc gaps. Not for unrelated refactoring.

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

Use when the user suspects no installed skill covers a task and wants proof. Names the owning skill or writes a missing-skill brief. Never routes or invokes the matched skill.

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

Use when a current decision needs pressure-testing until the rationale is clear to a skeptic. Not for tasks requiring source or remote-system changes.

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

Use when the user describes an AI workflow gap or uses an ambiguous cross-session reference such as 'the PR Bob mentioned'. Not for tasks that require source or remote-system changes.

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

Inspect one bounded Proto UI pull-request slice, produce canonical review input, and route each eligible exact head toward review and integration. Use for review queues, linked work, evidence gaps, merge conflicts, stale revisions, or portfolio health. This evidence leaf is read-only; authorized review and integration continue in their registered leaves.

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

Create or update a readable Proto UI legacy-contract projection for explanation or an explicitly accepted uncataloged gap. Use for internal contract prose, migration banners, rationale, or synchronized readable projections. Do not use when an applicable spec entity already owns the rule or when semantics are unsettled.

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

Refine an existing implementation plan with a second iteration. Re-analyzes the codebase for gaps, missing tasks, and wrong dependencies. Use after $aif-plan or to improve an $aif-fix plan. Optional +check flag validates refinements via a fresh-context subagent.

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

Analyze a job posting and map its requirements to the master resume as strong matches, partial matches, or honest gaps. Use when the user provides a job description or URL and wants a fit analysis before tailoring.

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

Create interview preparation from a job analysis, tailored resume, and master resume. Use when the user wants likely questions, truthful STAR answers, and ways to discuss gaps.

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