「adr」の検索結果

Deep agentic-flow@alpha integration implementing ADR-001. Eliminates 10,000+ duplicate lines by building claude-flow as specialized extension rather than parallel implementation.

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

15-agent hierarchical mesh coordination for v3 implementation. Orchestrates parallel execution across security, core, and integration domains following 10 ADRs with 14-week timeline.

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

Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architect...

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

Maxim L2 pack. Bundles: All six L1 packs. Primary framework: Behavioral Moat Framing Doctrine (ADR-007).

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

Pick the right writing voice for a task — which voice playbook applies, nk-writer invocation, brand-writer invocation, /mxm-voice-route. Lookup wrapper over the operator's voice selection authority.

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

Research synthesis from sources — "summarize these URLs or papers", "research this topic with these sources", "create a podcast about", "audio overview", "mind map", "quiz from these sources", "flashcards", "deep research on". Wraps Google NotebookLM via notebooklm-py.

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

Enterprise and solution architecture — system design, scalability, cloud strategy, digital transformation, data architecture, governance, technology strategy. Practitioner-level TOGAF, C4, ArchiMate, Zachman, Wardley mapping and ADR authoring.

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

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (GLOSSARY.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

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

Create an Architectural Decision Record (ADR) document for AI-optimized decision documentation.

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

Stress-test a plan against existing domain language, code behavior, and durable decisions. Use when the user wants DDD/domain-model grilling, glossary refinement, terminology challenges, context documentation, ADR candidates, or plan validation against a repo's language.

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

Complete guide for ASP.NET Core Web API integration testing. Use when performing integration testing on Web API endpoints or validating ProblemDetails error format. Covers WebApplicationFactory, IExceptionHandler, Testcontainers multi-container orchestration, Flurl URL construction, and AwesomeAssertions HTTP validation. Keywords: webapi integration testing, WebApplicationFactory, asp.net core integration test, webapi integration test, IExceptionHandler, ProblemDetails, ValidationProblemDetails, AwesomeAssertions, Flurl, Respawn, Be201Created, Be400BadRequest, multi-container testing, Collection Fixture, global exception handling

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

Check docs/ai/ spec files and ADRs for inconsistencies with the actual codebase. Report only, no modifications.

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

Check docs/ai/ spec files and ADRs for inconsistencies with the codebase, then fix all discrepancies.

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

Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.

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

Revise the Harbor Book so prose, drawings, and marginalia explain the same argument without unpublished development-document dependencies. Use for chapter additions, substantive rewrites, caption editing, visual exposition, and eliminating internal ADR citations.

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

Own whether a multi-document product-architecture binder is internally consistent, complete against its stated customer/contingency/architecture coverage, and honest about which older product ambitions it has absorbed, superseded, deferred, contradicted, orphaned, or rejected. Use when running a binder Architect of Record pass, before an implementation chain cites a binder chapter as ready, when a proof-gate owner is missing, or when reconciling the binder against the older ambition corpus (website, plans, examples, ADRs). NOT for auditing a single Claude Skill bundle's structure or frontmatter (use skill-hygiene), rendering a single-PM accept/reject verdict on one finished deliverable (use port-daddy-user-surrogate-pm-review), or sequencing/stewarding a roadmap's sidequests once a gap or operator decision has been surfaced (use legible-roadmap-with-sidequests).

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

Install Port Daddy's bounded interactive coordination hooks ("tentacles", from the Giant Squid Harness) into the INTERACTIVE sessions of agentic coding CLIs (Claude Code, Codex, Gemini, Antigravity/agy) by auto-detecting which CLIs are installed and writing PER-PROJECT hook config behind a runtime gate, so coordination fires only inside a Port Daddy project while the daemon is running — never machine- wide-always-on. Use when the user says "install port daddy hooks", "agent CLI hooks", "interactive session hooks", "make coordination hooks fire in interactive sessions", "codex/gemini/agy hooks", or "auto-detect agent CLIs". NOT for generic software/package installation; NOT for installing the Port Daddy daemon or `pd` CLI itself (delegate to the `port-daddy` skill / `pd setup`); NOT for MCP server setup (delegate to `pd mcp install`); NOT for authoring new skills (delegate to `skill-architect` / `skill-creator`); NOT for editing the tentacle scripts themselves (owned by the Giant Squid Harness program; this installer layer is pd-adr-090).

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