specification

Plugin specification from marketplace alvis in alvis/.agents. Commands read from the repo's manifest — yesterday.

Skills (7)

• implement-code

  Execute an approved specification work item from an authoritative local, inline, or Notion-backed contract through delegated coding, review, source-appropriate completion, and verified provenance. Use after plan-code approval, when resuming partial work, or when auditing delivered ticket work.

• mdc

  Read, edit, and author Theriety Notion-backed MDC files safely with native text tools while preserving the private parser grammar and ref identity. Use for company MDC body changes; keep transport and conflict orchestration in the Alvis specification skills.

• plan-code

  Build an implementation-ready plan from an approved specification inside an active work stream. Use to resolve the decision surface, define atomic implementation slices, and prepare verification without creating independent root planning or change artifacts.

• review-implementation

  Review implementation against an authoritative local, inline-origin, or Notion specification, coordinate the seven canonical review areas, and summarize dispositions in the active work item. Use for alignment, ticket validation, omissions, drift, and unsanctioned behavior.

• spec-code

  Design, update, or retrospectively document a technical specification from a user-selected local, inline, or Notion source through an active work stream. Keep approved specification content in the active work's spec/; keep Notion transport in sync-notion and implementation planning in plan-code.

• sync-notion

  Synchronize paired local files and Notion pages in a declared direction, validate opaque transport identity metadata, and coordinate guarded conflict resolution. Own transport and pairing; require an explicitly selected body-author capability before semantic body creation or change.

• sync-spec

  Materialize a required Notion specification into an active work directory or complete approved specification changes through an explicitly selected local transport pair. Use before specification planning, implementation, or review and when publishing a reviewed contract. Delegate transport and confl

Hooks (5)

• SessionStart

  [ -n "${PLUGIN_ROOT:-${GROK_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-}}}" ] || { echo "plugin root unset" >&2; exit 1; }; plugin_root="${PLUGIN_ROOT:-${GROK_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-}}}"; plugin_r

• SubagentStart

  [ -n "${PLUGIN_ROOT:-${GROK_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-}}}" ] || { echo "plugin root unset" >&2; exit 1; }; plugin_root="${PLUGIN_ROOT:-${GROK_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-}}}"; plugin_r

• UserPromptSubmit

  [ -n "${PLUGIN_ROOT:-${GROK_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-}}}" ] || { echo "plugin root unset" >&2; exit 1; }; plugin_root="${PLUGIN_ROOT:-${GROK_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-}}}"; plugin_r

• PreToolUse

  [ -n "${PLUGIN_ROOT:-${GROK_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-}}}" ] || { echo "plugin root unset" >&2; exit 1; }; plugin_root="${PLUGIN_ROOT:-${GROK_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-}}}"; plugin_r

• PostToolUse

  [ -n "${PLUGIN_ROOT:-${GROK_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-}}}" ] || { echo "plugin root unset" >&2; exit 1; }; plugin_root="${PLUGIN_ROOT:-${GROK_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-}}}"; plugin_r

Similar plugins