Agent Plugins Marketplace
← All plugins

specification

v1.0.0

Design specifications, architecture specs, requirements gathering, and technical documentation with Notion integration

CodexClaude Code7 Skills

By Alvis4 GitHub starsUpdated 4 hours ago

Directory evidence

Runtimes
Codex and Claude Code
Parsed components
7 skill or MCP entries
Source updated
Aug 26, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install plugin

Installs for the current user
codex plugin marketplace add IchenDEV/agent-plugin-mkt
codex plugin marketplace upgrade agent-plugin-marketplace
codex plugin add specification@agent-plugin-marketplace

Paste and run these commands in a terminal with Codex. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/alvis/.agents

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/specification/.

Plugin files

plugins/specification/
├── .codex-plugin/plugin.json
├── .claude-plugin/plugin.json
├── skills/implement-code/SKILL.md
├── skills/mdc/SKILL.md
├── skills/plan-code/SKILL.md
├── skills/review-implementation/SKILL.md
├── skills/spec-code/SKILL.md
├── skills/sync-notion/SKILL.md
└── skills/sync-spec/SKILL.md

Included Skills7

implement-codeskills/implement-code/SKILL.md

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

mdcskills/mdc/SKILL.md

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-codeskills/plan-code/SKILL.md

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-implementationskills/review-implementation/SKILL.md

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-codeskills/spec-code/SKILL.md

Design, update, or retrospectively document a technical specification from a user-selected local, inline, or Notion source through an active work stream and versioned derived docs. Use for specification authoring; keep Notion transport in sync-notion and implementation planning in plan-code.

sync-notionskills/sync-notion/SKILL.md

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-specskills/sync-spec/SKILL.md

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 conflicts to sync-notion.

Plugin manifests2

plugins/specification/.codex-plugin/plugin.json
{
  "name": "specification",
  "version": "1.0.0",
  "description": "Design specifications, architecture specs, requirements gathering, and technical documentation with Notion integration",
  "author": {
    "name": "Alvis"
  },
  "skills": "./skills/",
  "mcpServers": "./.mcp.json",
  "interface": {
    "displayName": "Specification",
    "shortDescription": "Requirements, architecture, and technical specifications.",
    "longDescription": "Discover requirements and author, synchronize, review, and implement architecture and technical specifications.",
    "developerName": "Alvis",
    "category": "development",
    "capabilities": [
      "Skills",
      "Hooks",
      "MCP"
    ],
    "defaultPrompt": "Help me discover or write this specification."
  }
}
plugins/specification/.claude-plugin/plugin.json
{
  "name": "specification",
  "author": {
    "name": "Alvis"
  },
  "dependencies": [
    "coding",
    "essential"
  ],
  "description": "Design specifications, architecture specs, requirements gathering, and technical documentation with Notion integration for knowledge management",
  "version": "1.0.0",
  "mcpServers": "./.mcp.json"
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[specification on Agent Plugins Marketplace](https://pluginsmp.com/plugins/specification)