anchors new

Emit the skeleton of an artifact (spec, feature, test, plan…) per the ruler.

Generates the frame of a unit artifact with the @anchors header and the
identity already resolved:

  anchors new spec Login --out src/screens/Login.spec.md      → new code + default sections
  anchors new spec Calc --preset backend-logic --out src/business-logic/Calc.spec.md
  anchors new spec Login --out <path> --with auth,deps
  anchors new spec Card  --out <path> --without overview
  anchors new feature Login --out <path> --code ABCD
  anchors new spec --list-sections    → sections (with "when to use") and presets of the kind

--out is mandatory: the artifact is born NEXT TO the unit it describes (the spec beside
the code, the feature beside the spec) — never at the repository root.

Kinds: action, feature, flow, plan, product, spec, test. A spec, plan, product, flow or action gets a new CODE
(unique in the map); feature and test get a REF (pointing at the spec). Use --code to pin
the identity by hand.

Usage

anchors new <kind> <name> [flags]

Flags

Flag	Default	What it does
--code		use this identity code (otherwise generate a unique one)
--list-sections		list the sections of the kind and exit
--out		output path, mandatory: next to the unit the artifact describes
--preset		section set of a unit kind (see –list-sections)
--root	.	project root
--with		add OPTIONAL sections (csv)
--without		remove DEFAULT sections (csv)

Subcommands

anchors new progress

Create the -progress.md of an existing plan (the STATE, outside the map).

Creates the progress companion of a plan that already exists.

A plan is DECISION; progress is STATE. While the phase checkboxes lived in the
plan, marking `- [x]` was ALTERING the plan — and that charged a revision to whoever only
finished a phase, besides knocking down the judgment of the spec that the phase
delivered (the edge stamp holds the rev of both ends).

The `anchors new plan` already creates the companion. This command is for the plans that
were born before:

  anchors new progress --for plans/0002-plataforma.md

It does not overwrite: the file holds state, and rewriting it would erase what was
already recorded.

Usage

anchors new progress --for <plano> [flags]

Flags

Flag	Default	What it does
--for		the plan whose progress will be created
--root	.	project root

Setup and artifacts — family

Commands of the same family — what tells each apart:

Command	What it does
anchors init	Configure the project (anchors.yaml) through questions and answers
anchors new	Emit the skeleton of an artifact (spec, feature, test, plan…) per the ruler
anchors code	Generate a unique identity code for a new unit
anchors guide	Print the Anchors guides for AI agents
anchors docs	Compile the documentation from the templates in doct/
anchors install-hooks	Install the git pre-commit that runs the gates over staged files
anchors migrate	Bring the Anchors files up to the current format
anchors settings	This agent’s LOCAL configuration — what is its own, not the project’s
anchors touch	Bump updated_at in the @anchors header of the files that changed