---
canonicalUrl: "https://www.hoalee.net/specgent/docs/overview"
title: "Specgent overview"
description: "What Specgent is, what it produces and where its work ends."
kind: "doc"
language: "en"
---

# Specgent overview

## Start here

Specgent is a context\-grounded product development specification system for Claude Code, packaged as a Claude Code plugin\. It carries one initiative from an idea, or from a requirements document or RFC written elsewhere, to a specification that a downstream planning tool can consume\.

These pages describe Specgent as it is implemented today\. It is pre\-release: no version has been published, so there is no released package to install yet\. See [requirements and status](https://www.hoalee.net/specgent/docs/reference/requirements)\.

## How the pieces fit

- **Operations\.** Eleven pipeline operations, each invoked by hand\. Workspace context comes first, and each later operation builds on what the chain already holds\.
- **One chain per initiative\.** The chain starts at whatever you already have: an idea, a PRD or an RFC\. Levels above your entry point stay empty by design\.
- **Sealed revisions\.** Every output is sealed into a content\-addressed store\. A later revision is a new revision; nothing overwrites an accepted one\.
- **Independent review\.** A PRD and an RFC each need an independent review whose verdict names the exact revision it judged\.
- **Derived readiness\.** No operation declares a Feature ready\. Readiness is computed from the recorded history, and it moves backwards when the facts do\.

## Scope

Specgent produces specifications\. It does not implement them\. Its readiness vocabulary stops at `development-ready`; implementation, testing and release belong to the tools and people downstream of it\.

## Where each page goes

- [The eleven operations](https://www.hoalee.net/specgent/docs/guide/lifecycle) walks the pipeline in order\.
- [Reviewing and refining](https://www.hoalee.net/specgent/docs/guide/review-and-refine) covers the review loop beside the pipeline and how approval works\.
- [Handing off to planning](https://www.hoalee.net/specgent/docs/guide/handoff) states what a downstream tool consumes and what Specgent never provides\.
- [Commands](https://www.hoalee.net/specgent/docs/reference/commands) lists every operation and administrative command\.
- [Security boundaries](https://www.hoalee.net/specgent/docs/reference/security) separates what is enforced from what is only instructed\.
- [Glossary](https://www.hoalee.net/specgent/docs/reference/glossary) defines the terms these pages use\.