Skip to the content.

CLike Harper Extend Feature

Purpose

Harper Extend introduces the /extend command for controlled backlog evolution in an existing CLike/Harper project.

It appends new requirements to an already generated PLAN.md and plan.json without regenerating or mutating consolidated requirements.

The command is designed for projects that have already moved through IDEA β†’ SPEC β†’ PLAN β†’ KIT β†’ EVAL β†’ GATE and need to add new REQs after a stable anchor, for example after REQ-006.

Plan-only append vs next release. /extend appends REQs to the current plan. To evolve a delivered project to its next release β€” new needs merged into IDEA, SPEC and TECH_CONSTRAINTS, REQs typed ADDED / MODIFIED / REMOVED, release folders docs/inputs/vN/ and docs/reference/vN/ β€” use /idea --extend, the cascade mode of the same phase (see commands.md and architecture/ADOPT_AND_IDEA_EXTEND.md Β§12). This page describes /extend; the cascade shares its guard and adds its own rules.

Public Commands

/extend
/extend REQ-007 "ATDL v1 schema, validator and compiler"
/extend --after REQ-006
/extend --after REQ-006 --from attachment
/add-req

/add-req is an alias. The canonical phase and command remain extend.

Pipeline Position

IDEA β†’ SPEC β†’ PLAN β†’ EXTEND β†’ KIT β†’ EVAL β†’ GATE β†’ FINALIZE

EXTEND is optional and repeatable.

It is not a replacement for /plan. It is an append-only evolution phase.

Core Guarantees

Read Inputs

Required:

docs/harper/PLAN.md
docs/harper/plan.json

Optional, when present:

docs/harper/SPEC.md
docs/harper/IDEA.md
docs/harper/TECH_CONSTRAINTS.yaml
docs/harper/lane-guides/*.md
.clike/skills/**
.clike/packs/**
.clike/design-profiles/**
attachments

Written Outputs

Always:

docs/harper/PLAN.md
docs/harper/plan.json
docs/harper/EXTEND_<YYYY-MM-DD>_<FIRST_REQ>_<LAST_REQ>.md

Conditionally:

docs/harper/SPEC.md
docs/harper/lane-guides/<concern>.md

Forbidden by default:

src/
test/
tests/
runs/kit/
runs/eval/

Append-Only Policy

/extend must not rewrite existing REQs.

Default behavior:

REQ-001..REQ-N: read-only
REQ-N+1..REQ-M: appended

Existing REQ objects in plan.json must retain their semantic content.

Existing REQ sections in PLAN.md must not be rewritten. Shared sections such as dependency graph, milestone/backlog, and verification checkpoints may be extended only to include the new REQs.

SPEC.md Update Policy

SPEC.md is updated only when the new requirements add at least one of the following:

The safest default is to append a section such as:

## Extension Scope β€” REQ-007..REQ-009

instead of rewriting consolidated SPEC content.

Lane-Guide Update Policy

Lane-guides are concern-oriented, not language-oriented.

Good lane examples:

workflow-dsl
operational-registry
risk-policy

Bad lane examples when used as implementation inference:

node
python
java

A lane-guide is created or updated only when the extension introduces a new capability concern or new evaluation guidance.

Cloud Execution Path

The cloud path is responsible for requirement interpretation and structured document generation.

The orchestrator sends the cloud model:

The cloud response must produce file artifacts only under allowed Harper documentation paths.

Local-Agent Execution Path

The local-agent path is responsible for repository-local patching while preserving exact file structure.

The orchestrator emits an AGENT_EXTEND_CONTEXT.json package with:

The agent may write only:

docs/harper/IDEA.md
docs/harper/PLAN.md
docs/harper/plan.json
docs/harper/SPEC.md
docs/harper/lane-guides/
docs/harper/EXTEND_*.md
docs/harper/TECH_CONSTRAINTS.yaml   (cascade only: /extend gets it restored)

Validation Rules

After /extend, CLike must validate:

The extension enforces the plan rules deterministically before keeping the result (extensions/vscode/extend-guard.js, cloud and local agent alike):

The cloud prompt carries the request of the command (anchor, requested REQ id, text, attachments) in an EXTEND REQUEST section, so the cloud and the local agent receive the same instructions.

Audit Report

Example:

docs/harper/EXTEND_2026-05-19_REQ-007_REQ-009.md