---
title: "specful"
description: "Skills for authoring and reviewing Specful artifacts, planning and implementing changes, and operating the CLI."
canonical: https://agentpluginsdirectory.com/plugins/specful
last-updated: 2026-10-21
---

# specful
Skills for authoring and reviewing Specful artifacts, planning and implementing changes, and operating the CLI.
- Slug: specful
- Publisher: unkos-dev
- Repository: https://github.com/unkos-dev/specful
- Manifest: plugin/plugin.json
- License: Apache-2.0
- Category (editorial): documentation
- Skills: 11 (specful-adr, specful-design, specful-implement, specful-index, specful-onboard, specful-plan, specful-requirement, specful-review, specful-show, specful-trace, specful-validate)
- MCP servers: 0
- Stars: 0
- Repository created: 2026-08-14
- Repository last pushed: 2026-10-20
- Publisher type: Organization
- Listing: https://agentpluginsdirectory.com/plugins/specful
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What specful does, in the publisher's words

> Re-spec your repository.

Specful is a portable convention for keeping software requirements, design documentation, and decisions current, connected, and usable by people and coding agents, served by a single-binary CLI.

The convention is the product. A repository that follows the layout, templates, and writing model is a Specful repository, readable and navigable with ordinary files, Git, and text search. The specful CLI mechanises what the convention cannot deliver by hand at acceptable cost: allocating stable identifiers, regenerating navigation views, and validating the repository.

- Requirements define what the software must do now.
- Design descriptions explain how the software works now.
- Architecture Decision Records preserve the rationale for durable decisions.
- Private plans coordinate transitions without becoming permanent public documentation.
- Markdown and structured metadata in the adopting repository are canonical.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/unkos-dev/specful/HEAD/README.md

## Skills

- specful-adr: Use when recording a durable decision as a Specful ADR (architecture decision record), or superseding an accepted one.
- specful-design: Use when writing or updating a Specful Design: documenting how a subject of the system works, or connecting a Design to the Requirements it satisfies.
- specful-implement: Use when the user asks to implement, execute, resume, or continue a saved change plan or arc plan step by step.
- specful-index: Use when the navigation indexes or catalog under `docs/specs/` are missing or out of date after adding or editing a Requirement, Design, or ADR, or when checking whether they are.
- specful-onboard
- specful-plan: Use when a change needs a persistent implementation plan, unresolved design choices must be settled before planning, or an arc must coordinate multiple deliverables.
- specful-requirement: Use when writing or updating a Specful Requirement: a new normative obligation, or a change to what the software must do.
- specful-review: Review a Specful Requirement, Design, ADR, or change for consequential substantive defects.
- specful-show: Use when looking up the catalog record for a specific Requirement, Design, or ADR identifier.
- specful-trace: Use when following requirement-to-design links for a specific Requirement identifier, checking whether a Requirement has a satisfying Design, or listing the artifacts that cite an ADR.
- specful-validate: Use when checking whether Specful Requirements, Designs, and ADRs pass schema and cross-reference validation, before committing a change to any of them, or when wiring the checks into an agent harness's hooks.

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.