1,530 件 ・ 関連度順
概要と使いどころ
Goal-integrity skill. Use for backend/API/persistence, preserve/do-not-change, tests/validation, mocks, rework, multi-part requests. Emits Goal Contracts, Deviation Notices, Phase Checks, Final Audits. Skip for Q&A or trivial edits.
日本語の概要は準備中です。原文の説明を表示しています。
Heuristic-first software surgery for proof-backed, minimal-diff implementation: Contract to Invariants to Cut Rationale to inevitable incision to Proof. Use when users say "run /tw-tk", "patch-first", "keep the diff small", "state contract + invariants", "one clear incision", "fix it with a validation signal", or orchestration cues like "workers use /tw-tk" / "internally use /tw-tk".
日本語の概要は準備中です。原文の説明を表示しています。
Load when authoring/reviewing commit messages or PR titles/descriptions, or replacing a materially diverged phase commit contract; not for ordinary implementation or executing an unchanged approved contract.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from MIL-STD-881F (13 May 2022), DoD Standard Practice for Work Breakdown Structures for Defense Materiel Items. Use for Program/Contract/Subcontract WBS construction, 100% rule and dictionary discipline, commodity appendices A–J, Common Elements (K), sustainment CES reporting (L), Government ST&E (M), and RFP/post-award implementation. Technical planning & WBS and PM/measurement focus—not a cost manual substitute for CAPE policy.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from the GAO Agile Assessment Guide (GAO-24-105506, 2023). Use for assessing and managing Agile software development in federal programs: the Agile Manifesto and framework family (Scrum, Kanban, XP, SAFe, DA, DSDM, Lean, DevOps); the three adoption perspectives (team dynamics, program operations, organization environment); requirements decomposition (epics, features, user stories, INVEST, MoSCoW, definition of done); Agile-aware federal contracting (FAR, modular contracting, SOO/PWS/SOW, product owner vs. COR); program monitoring and control (WBS, cost, schedule, EVM at the feature level); Agile metrics (velocity, lead/cycle time, CFD, burn charts); and the auditor's key-question bank. Oversight- and acquisition-oriented: it tells you how to *assess and govern* Agile programs, not how to code. Thin on hands-on engineering practice, deep cost/schedule checklists (see gao-cost, gao-schedule), and any non-US-federal context.
日本語の概要は準備中です。原文の説明を表示しています。
Compares one policy against one requirement set (standard, regulation, contract schedule or customer requirement) clause by clause and returns a draft gap review: each requirement element, the policy clause that appears to address it, an apparent match state, and every gap as a question with the clause reference on both sides. Never concludes that the policy complies; the owner decides. Use when the user asks to "gap our policy against the standard", "map this policy to the regulation clause by clause", "check the security policy against the customer's contract schedule", "compare our policy with the new edition" or "where does our policy fall short of the requirements". Do not use for mapping a requirement to the operating controls that implement it, use controls-gap-pack instead; for what a regulatory change means for the organisation, use regulatory-change-impact-note. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Triages an incoming non-disclosure agreement against the organisation's written standard NDA positions and returns a DRAFT triage pack: a clause-by-clause deviations table with a severity band, a suggested response per clause quoted from the positions document, open questions and a governing-law flag, all for counsel to decide. Never gives legal advice or an acceptability call. Use when the user asks to "triage this NDA against our standard positions", "screen this confidentiality agreement before it goes to legal", "red-flag this mutual NDA", "first-pass the counterparty's NDA" or "is this NDA standard or does it need counsel". Do not use for a full review of an MSA, SOW, licence or any whole contract, use contract-review-pack instead; for one clause lined up across several documents, use clause-comparison-table. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews a proposal, business case, deck or vendor contract in character as a Head of Procurement archetype and returns a DRAFT review in the chat with a verdict, findings that cite the exact passage or clause, commercial risks, what would change the verdict and five interrogation questions. Use when the user asks to "review this from a procurement angle", "what would procurement say about this proposal", "pressure-test this vendor contract commercially", "find the holes before the sourcing committee" or "check the renewal terms like a Head of Procurement would". Do not use for liability, IP, regulatory or signing-authority questions, use general-counsel-reviewer instead; for whether the spend fits the budget, use cfo-reviewer; for vendor security, use ciso-reviewer. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Goal-integrity skill. Use for backend/API/persistence, preserve/do-not-change, tests/validation, mocks, rework, multi-part requests. Emits Goal Contracts, Deviation Notices, Phase Checks, Final Audits
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "draft an influencer contract", "review these agreement terms", or "build a partnership template"; produces a full influencer agreement framework (scope, compensation, usage rights, exclusivity, FTC disclosure), a clause-by-clause review with red flags, and a negotiation cheat sheet. Not for outreach negotiation before a deal exists — use outreach-manager. 达人合同/合作协议条款审查
日本語の概要は準備中です。原文の説明を表示しています。
Ensure OpenAPI specs define consistent request/response schemas, error model, auth, pagination, and backward compatibility.
日本語の概要は準備中です。原文の説明を表示しています。
スキーマ/データ移行の安全性を framework 非依存で審査する。破壊的スキーマ変更・ロック誘発・backfill・ロールバック可逆性・expand-contract の段階適用を、prisma / typeorm / Rails / Django / Alembic / 生 SQL などに横断適用する。
Detect null/undefined/empty handling gaps where callers or consumers may receive unexpected nullish values.
日本語の概要は準備中です。原文の説明を表示しています。
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
日本語の概要は準備中です。原文の説明を表示しています。
Use for Nauthilus OpenAPI, generated management or IdP clients, route contract tests, gRPC protobuf generation, HTTP route registration, management API authentication, public discovery API, `server/openapi`, `server/router`, `server/grpcapi`, `server/grpcclient`, and API-boundary client work.
日本語の概要は準備中です。原文の説明を表示しています。
Safely evolve shared contracts with consumer discovery, migration tests, versioning checks, and downstream spec cascade validation
日本語の概要は準備中です。原文の説明を表示しています。
Manage API versioning and evolution with URL/header/query strategies, deprecation workflows, breaking change classification, sunset headers, and consumer-driven contract testing. Use when designing versioning strategy, deprecating endpoints, or evolving API contracts.
日本語の概要は準備中です。原文の説明を表示しています。
Expert en automatisation documentaire avancée (templates, merge fields, e-signatures, PDF generation, DocuSign, contract lifecycle)
日本語の概要は準備中です。原文の説明を表示しています。
Document Automator IA — Expert en automatisation documentaire (PDF generation, contract templates, e-signatures, DocuSign, Notion API)
日本語の概要は準備中です。原文の説明を表示しています。
Expert en négociation de contrats v2 (terms, SLAs, renouvellement, PI, responsabilité, contexte juridique DZ)
日本語の概要は準備中です。原文の説明を表示しています。
Expert en négociation de contrats (terms, SLAs, renewal, upsell, legal review, redlines)
日本語の概要は準備中です。原文の説明を表示しています。
Blockchain Developer IA — Expert en développement blockchain (Solidity, smart contracts, Web3.js, DeFi, NFTs)
日本語の概要は準備中です。原文の説明を表示しています。
Implement data quality validation with Great Expectations, dbt tests, and data contracts. Use when building data quality pipelines, implementing validation rules, or establishing data contracts.
日本語の概要は準備中です。原文の説明を表示しています。
Use when adding or changing REST endpoints or the OpenAPI contract — deriving endpoints from the Lean commands and views, writing documents/codebase/openapi.yaml first, then regenerating the backend controller interfaces and the frontend client.
日本語の概要は準備中です。原文の説明を表示しています。