Results for “attribute-agreement”

UAT Sign-off

Compare, cross-review, and merge competing plans from multiple agents into one executable direction with a clear handoff.

Use this when the team needs to define permissions, roles, membership rules, resource ownership, or action-level authorization separate from authentication choice. Trigger on requests about access models, RBAC, ABAC, tenancy, or protected operations.

Use when designing or auditing AI product human-in-the-loop — write approval, proposal accept/reject, action confirm, spend caps, run detail, memory capture, or any AI action with irreversible blast radius. Trigger on confirmation UX, undo, cost-before-act, show-the-plan, citations, or keeping the owner in control.

Provides guidelines and best practices for aggregates and aggregate roots, referencing detailed documentation.

Action (apaz-action)

Generates structured Given/When/Then acceptance criteria for a user story or feature slice. Use when translating product requirements into testable scenarios that cover the happy path, edge cases, error states, and non-functional expectations for engineering handoff and QA.

Rule (afak-rule)

Action (afaz-action)

Drafts intellectual property assignment agreements transferring patents, trademarks, copyrights, and trade secrets. Covers conveyancing language, registration recordation, consideration, representations and warranties, and post-closing obligations. Use when drafting IP assignments, asset purchase IP transfers, or technology transfer documents.

融合分类系统与规则抽象能力，构建基于规则的分类体系，支持规则驱动的分类需求和规则执行。

Imported skill approval from langchain

Give a decisive, project-grounded point of view in the subject's own shape: a graded verdict on an external-adoption question, a holistic take on a document, or a position on a user-supplied approach set. Use for a solo POV, a mid-session second opinion, a named-peer cross-check, any request to consult other models or reconcile their opinions, an `oracle` panel, or a correction-cost-gated proactive cross-check offer. Not for findings review (use ce-doc-review), neutral explainers, or generating options (use ce-ideate or ce-brainstorm).

Record a decision: finalized → ADR (optionally rule + guide or spec + plan); open proposal → RFC. Use for 'we decided', 'record this decision', 'make it a standard', 'draft an RFC', 'should we switch to Y'. Not for feature planning or documenting existing code.

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md. Identifying inconsistencies, duplications, ambiguities, and underspecified items.

Walk a business/UAT approver through a plain-language demo of a verified feature and capture business acceptance signoff.

ateam-spec

Ownership models are usually inherited rather than chosen, and the inherited one