「canon」の検索結果

[Workflow] Use when activating the Spec to PBI Backlog workflow to convert canonical tech-free Feature Specs into complete, prioritized, dependency-aware PBIs and stories.

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

[Workflow] Use when activating the Idea-to-Spec workflow — turn a raw idea/vision/problem into ONE canonical (provisional) Feature Spec. STOPS at the reviewed spec; chain workflow-spec-to-pbi for a backlog. For code→spec use workflow-code-to-spec.

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

[Workflow] Use when activating code-to-spec development — author/maintain the single canonical Feature Spec FROM existing code, keeping spec, implementation, and tests synchronized. For idea→spec (no code yet) use workflow-idea-to-spec.

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

[Code Quality] Use to validate a spec artifact's decisions with the user across three contexts — a freshly-authored Feature Spec (idea-to-spec), an existing canonical spec before PBI decomposition (spec-to-pbi), or a refined idea + §8 test-specs (idea-to-pbi deep mode). Detects the context, walks every applicable validation category, and runs an exhaustive but budget-bounded blocking clarification gate so every non-obvious or conflicting decision is confirmed before the artifact drives downstream work.

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

[Documentation] Use when (re)generating the DERIVED technical spec view over code + tests, or reporting canonical §8 TC/test-code drift. A GENERATOR — it projects code + tests into a regenerable per-component view and NEVER authors business content. Modes generate|audit|sync. Per-mode procedure lives in references/{author,sync}.md.

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

[General] Use when you need to (re)generate a DERIVED navigation index, cross-capability ERD, or reimplementation guide assembled FROM the canonical Feature Specs under docs/specs/**. Never extracts a separate A-E engineering tree.

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

Normalizes company names, industries, domains, locations, and descriptions. Use when the user provides company records and wants consistent canonical fields with confidence and unresolved items flagged.

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

Audit and safely clean local project repositories or workspaces with excessive generated files, old project residue, dirty Git status, stale worktrees, build caches, duplicate nested projects, confusing roots, or agent context/token waste. Use when the user asks to organize a repo, remove useless files, classify valid project files, clean untracked/deleted files, reduce disk usage, migrate from an old repo layout to a canonical project, or prepare a repository for future Codex/agent work.

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

Collect project brief and stack choices, then output canonical project-config.json for downstream web-builder skills.

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

X 長文投稿のルールがどのファイルにあるか迷ったとき、同じ規定が複数箇所に見えてどれが正か判断する必要があるときに読む。

Audit and harden Convex authorization: identity-from-arg impersonation, missing per-document ownership checks, PII-leaking public queries, and writes into containers the caller doesn't own. Deterministic scan + canonical requireIdentity/requireOwner fix + tsc verify. Use for 'secure my app' / 'audit auth' / 'who can access this data', not generic code review.

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

Draft public Tamanu release notes for a given version. Use when the user wants release notes for a Tamanu release (e.g. "draft release notes for v2.45"). Pulls work from the specs and code that landed in that version's release/X.Y branch, plus the matching issues in the trackers (Linear's Tamanu team and Workhorse's Tamanu workspace), reconciles them, and writes docs/release-notes/vX-YY.md in the canonical v2.44 format for project managers and system administrators, plus a styled HTML rendering at .workhorse/design/designs/vX-YY-release-notes.html. Not for developer changelogs or QA test scoping (use scope-tamanu-release-tests for the latter).

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

Update docs, playbooks, shims, generated docs, and alignment checks so public instructions route to the right canonical sources.

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

Keep decision maps as concise routers from decisions to canonical documents and validation guardrails.

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

Repair confirmed architecture drift in small batches while preserving public canon and avoiding broad opportunistic refactors.

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

Run an offline ASO audit on canonical App Store metadata under `./metadata` and surface keyword gaps using Astro MCP. Use after pulling metadata with `asc metadata pull`.

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

Sync, validate, and apply App Store metadata with the current asc canonical metadata workflow. Use when updating metadata, localizations, keywords, or migrating legacy fastlane metadata.

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

Advisory checkpoint for deciding whether planning-document edits should be split into a separate planning branch/PR. Use only when the user explicitly asks where to commit `memory/SPEC.md` or `memory/PLAN.md` changes, mentions planning-doc merge conflicts, asks for a planning PR, or instructs you to prepare/submit one. Do not trigger for ordinary ln-* planning edits, one-line status updates, or routine canonical reconciliation.

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

Refresh `memory/SPEC.md` and `memory/PLAN.md` in mature mode — restore canonical truth, archive retired plan history, delete stale derivative artifacts, and flag drift against code.

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

Knowledge base from the NIST Framework for Cyber-Physical Systems (SP 1500-201/202/203, v1.0, 2017). Use for engineering and analyzing cyber-physical systems (CPS) and IoT: the CPS Framework's aspect × facet grid (nine aspects of concern examined through conceptualization, realization, and assurance facets), cross-property trustworthiness risk management (safety/security/privacy/reliability/resilience together), data interoperability (syntactical/semantic/contextual, canonical models, identifiers, provenance), the timing aspect (time-interval classes, time domains, time-aware networking) and secure/resilient time (GNSS jamming/spoofing, PTP/NTP attacks, holdover, the clock-error model and Allan/MTIE metrics), plus the use-case requirements method. Bridges IT and OT under a clock. Scope limits: a 2017 living/draft document, thin on post-2017 standards and on detailed control catalogs; it names but does not reproduce ISO/IEC/IEEE 42010 and 15288 process text or permission-licensed third-party figures.

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

Knowledge base synthesized from the Guide to the Systems Engineering Body of Knowledge (SEBoK) v2.14 by the BKCASE Project. Use for the established systems-engineering canon: SE fundamentals and foundations (systems science, systems thinking, the systems approach, modelling/MBSE), the life cycle (ISO/IEC/IEEE 15288/24748/24774 process, development & agile approaches, model selection/tailoring), technical management, concept definition, architecture/realization (the Vee), V&V, maintenance/sustainment, SE standards, and the application contexts (product, service, enterprise, systems-of-systems, healthcare), plus enabling SE (business/team/individual), related disciplines, quality attributes/specialty engineering, implementation examples, and emerging knowledge. Good for grounding background, vocabulary, and prior-art positions across all eight SEBoK Parts. SCOPE LIMITS: this pack is SEBoK v2.14 only (released 2026-05-18); it synthesizes and signposts rather than reproducing the source — it does not reproduce ISO/IEC/IEEE standard text, is a curated guide (not a complete textbook), and is thin on AI-integration depth (Part 8 is a staging area, not settled practice). LICENCE: content is CC BY-NC-SA 3.0 — non-commercial use only, attribution to the BKCASE Project required, share-alike obligations carry forward.

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

Knowledge pack from 'Towards Digital Engineering: The Advent of Digital Systems Engineering' (Huang et al., Old Dominion University, arXiv:2002.11672, 2020). Use when reasoning about digital engineering, the DoD Digital Engineering Strategy and its five goals, the Authoritative Source of Truth, digitalization vs. digitization, digital augmentation, digitalized models, provenance, unique identification, and the four-level (vision/strategy/action/foundation) DSE research framework. Covers the conceptual/vision layer of the field. SCOPE LIMITS: this is a single ~28-page vision paper, not a methods handbook — it is thin on step-by-step procedures, tooling, case studies, and quantitative evaluation, and it predates 2020 so it does not cover later digital-engineering standards or recent AI/LLM advances. Use the sebok pack for established SE canon and MBSE depth.

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

Close a work session properly: reconcile it against the wider collaboration, inventory what was actually built from git log and recently-touched files, summarize the arc, classify each artifact as keep, one-off or promote-to-permanent, route the durable ones to memory, canon or a new skill, save the retro as a vault note, and hand back an enriched /compact block so working memory shrinks without losing the thread. Triggers: "/retro", "/rr", "wrap up the session".

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

Route a new rule, preference or policy edit into every home it belongs in (always-loaded canon, memory, the behavioral codex, a skill, a hook) and leave a trace in the always-loaded layer so parallel sessions pick it up on their own. Flow: dedup recall, classify by form, write to all homes, back up, report. Triggers: "/intake", "record this rule", "route this to its homes".

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