Plan A Feature

Project Context

• CLAUDE.md: !find . -maxdepth 1 -name "CLAUDE.md" -type f
• project-discovery.md: !find . -maxdepth 3 -name "project-discovery.md" -type f
• personal config directory: !bash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh" 2>/dev/null || echo "$HOME/.claude"
• project .han/config.md: !cat .han/config.md 2>/dev/null || echo ""

As your first action, use the Read tool on .han/config.md inside the personal config directory path above. A read that returns no file is no personal configuration: continue silently. When that file or the project .han/config.md probe supplies content, apply it per config-rule.md, which governs precedence between the two files, relative-path resolution, and what to do with a file that reads but cannot be used.

Operating Principles

• Interview relentlessly, but explore first. If a question can be answered by reading the codebase, project docs, coding standards, ADRs, or existing feature specs — or by querying a read-only tool already available to this session that authoritatively answers it (for example a connected schema or data-source tool) — explore instead of asking. Only surface questions that genuinely require the user's judgment. The connected-tool path is gated on availability, not on a fresh judgment: use it only when such a read-only tool is actually permitted to this skill; if none is available, ask the user as today (see Step 4).
• Walk the design tree. Decisions have dependencies. Resolve foundational decisions first (what the feature does, who uses it, what outcome it produces). Then descend into dependent decisions (flow, states, edge cases, coordination points). Never ask a dependent question before its parent is settled.
• Recommend, then ask. For every question surfaced to the user, provide a recommended answer with rationale grounded in evidence (code, docs, conventions, or stated goals). The user can accept, redirect, or provide a nuanced response.
• Behavior, not implementation, in the spec. The specification captures WHAT the feature does, for WHOM, and WHY — at a level a reader who has never opened the codebase can understand. Language primitives, file/line references, function or class names, library mechanics, implementation patterns, and internal env/flag names DO NOT appear in feature-specification.md. Product-level subsystem names ("events processing system", "backend service"), user-facing UI vocabulary (popover, modal, toast), URL paths, behavioral verbs, and user-observable states DO. Technology brand names generalize one level up (NATS → "events processing system"; PostgreSQL → "database"; Redis → "cache"). This rule is language-agnostic — it applies equally to Go, Rails, Node, Python, Swift, Kotlin, and frontend JavaScript code. Any examples given in references or templates are illustrative, not an exhaustive deny-list.
• Load-bearing mechanics go in feature-technical-notes.md, not the spec. When a mechanic is load-bearing for a behavior — meaning the behavioral commitment in the spec is only correct because of that mechanic (ordering, durability, consistency, visibility timing) — the behavioral consequence goes in the spec sentence, and the mechanic goes in a T# note linked inline from that sentence. The tech-notes file is LAZILY created — it exists only when at least one load-bearing mechanic qualified. Mechanics that are discoverable from the code repo (an existing pattern, an in-use library, a documented convention) do NOT belong in the tech-notes file either — plan-implementation will find them from the code. Mechanics that do not affect observable behavior are pure implementation and belong in the implementation plan, not here.
• YAGNI is a first-class operating principle. Apply the evidence-based YAGNI rule in yagni-rule.md to every commitment the spec carries. An item with no accepted evidence is demoted to ## Deferred (YAGNI) with its reopening trigger, never silently dropped and never silently kept. An item with evidence gets the simpler-version test.
• Evidence quality is the companion principle. Apply evidence-rule.md alongside YAGNI. YAGNI gates inclusion; this one characterizes the quality of what each commitment rests on, through trust classes, the corroboration gate on web claims, and a distinct label for no evidence at any tier.
• The run stays inside the boundary it descends from. The skill records the work item's stated scope and exclusions before the interview, per planning-boundary-rule.md. Every commitment is checked against it, and anything the boundary excludes lands in a visible cut list, per scope-justification-rule.md.
• Visual material the user supplies is kept, and reaches every reviewer. Persist it beside the spec as it arrives, never at document-write time, and pass its paths in every reviewer's brief. The session context is the only copy until it reaches disk, and a compaction destroys it. The boundary rule owns the convention.
• Questions to the user arrive one at a time, led by the consequence. Per operator-escalation-rule.md. The opening confirmation turn is the one exception, and the one turn that carries more than one ask.

Plan a Feature

Step 1: Capture the Feature Request and Output Location

Read the user's argument and conversation context to extract the feature being planned. If the request is too thin to start (e.g., just "plan a feature"), ask the user for a one-to-two-sentence description of what the feature does and what outcome it produces — nothing else yet.

Resolve the output location:

• If the user specified a folder path, use it.
• Otherwise, propose a folder name of 3 to 5 words in kebab-case (e.g., docs/features/user-invite-flow/, docs/plans/bulk-export-jobs/). Prefer placing it under an existing documentation root discovered via CLAUDE.md's ## Project Discovery section, project-discovery.md, or Glob fallbacks (docs/features/, docs/plans/, docs/).
• Confirm the folder name with the user before creating files. If the folder does not exist, create it.

Up to four files will be written. The primary spec lives at the root of {folder}/; the companion artifacts live in {folder}/artifacts/ to keep the planning folder uncluttered:

• {folder}/feature-specification.md — the primary behavioral spec. Always written.
• {folder}/artifacts/decision-log.md — the full decision history with rationale, evidence, and rejected alternatives. Always written.
• {folder}/artifacts/team-findings.md — review-team findings and how each was resolved. Always written.
• {folder}/artifacts/feature-technical-notes.md — load-bearing mechanics that were captured because they were needed to correctly specify a behavior. Lazily created — written only if at least one T# qualifies during the interview (Step 4) or finding resolution (Step 7). If no T# qualifies, the file is never created and the spec contains no T# links.
• {folder}/artifacts/scope-boundary.md — the boundary record. Always written, by Step 1.5.

One more folder appears when the user supplies visual material:

• {folder}/ui-designs/ — the visual material itself, one file per item, named for the state it depicts.

Create the artifacts/ subfolder before writing the companion files if it does not already exist.

The files cross-reference each other. The main spec cites decisions with inline parenthetical links like ([D4](artifacts/decision-log.md#d4-invite-expiration-window)) and cites technical notes (when the file exists) with inline parenthetical links like ([T3](artifacts/feature-technical-notes.md#t3-ack-ordering)). The decision log, findings log, and tech-notes file (all siblings inside artifacts/) cross-link through Driven by findings: / Linked technical notes: / Affected decisions: / Affected tech-notes: / Supports decisions: fields, and all reference back into the spec with ../feature-specification.md paths.

Step 1.5: Read and Record the Scope Boundary

Read ../../references/planning-boundary-rule.md for the record's name, its sections, and the accepted visual-material file set. Establish the boundary before you discover anything or ask anything.

A record already exists at {folder}/artifacts/scope-boundary.md. Read it and use it. Do not re-ask anything it answers, including the direction-of-travel question: a recorded answer of any kind is never re-asked.

No record exists. Identify the work item this feature descends from — a ticket, an issue, a pull request, or a written request the user typed — read it, and record its stated scope and exclusions word for word. When no work item exists, record that explicitly, along with the statement that the user's request is the only boundary this run has. The read does not traverse outward: a linked, sibling, or closed item is not scope evidence for the item in hand. There is no tool here that reads a tracker, so you will often be recording the user's own words; record which it was.

Then take one confirmation turn before Step 2 begins. It restates the recorded boundary in the user's own terms, names any visual material you kept, and asks the direction-of-travel question with its subjects named from the work item: are the specific things it named being deprecated, replaced, or migrated away from? This turn is a confirmation rather than an escalation, and the one turn that carries more than one ask. When the user hands you a work item that conflicts with the recorded one, surface the conflict here and ask which governs, rather than silently overwriting or trusting the record.

Persist every piece of visual material the user supplies into {folder}/ui-designs/ as it arrives, named for the state each one depicts, and note each item into the record's Visual Material Received section as you keep it. When the host never made an item reachable as a file, name which items you could not keep and ask for them through the single stop, while they are still recoverable.

Source the explanation standard by invoking han-communication:explanation-guidance before you write the confirmation turn, and again before any escalation or stop later in the run.

Step 2: Discover Before Asking

Before asking the user anything beyond the initial framing, explore the codebase and project documentation to gather context that will answer as many design-tree questions as possible. Use Glob and Grep to find:

• CLAUDE.md, AGENTS.md, and any project-discovery.md — tech stack, constraints, conventions.
• ADRs in docs/adr/ or docs/architecture/decisions/ — prior architectural decisions the feature must respect.
• Coding standards in docs/coding-standards/ or .github/CODING_STANDARDS.md — rules the feature's design must align with.
• Existing feature specifications or PRDs — tone, structure, level of detail the team expects.
• Code adjacent to what the feature touches — current behaviors, patterns, integration points.

A connected read-only tool that authoritatively answers a design-tree question counts as a source here, on the same terms the operating principles set: read-only, never writing or changing state.

Record what was found (file paths) and what was not found. Missing standards are themselves findings that inform the feature spec.

Step 3: Build the Design Tree

Enumerate the decisions the feature needs in dependency order. A decision is a question whose answer shapes behavior. Group them into tiers:

1. Foundational — What is the feature? Who uses it? What outcome does it produce? What triggers it? What does "done" look like?
2. Behavioral — What are the primary and alternate flows? What states does the feature move through? What coordinations between actors, services, or subsystems are involved?
3. Boundary — What edge cases, failure modes, and rollback behaviors must be specified? What is explicitly out of scope? What does the system do when inputs are malformed, missing, or adversarial?
4. Interaction — If there is a user interface or API surface, what is the interaction model? What affordances, feedback, and error states must exist?

Do not pre-populate the tree with implementation detail. Keep each node as a behavioral question with a candidate answer.

Step 4: Interview Loop — One Branch at a Time

For each decision in dependency order:

1. Try to resolve it from evidence. Re-check the codebase, docs, standards, ADRs, and already-settled decisions. If a read-only tool that authoritatively answers the question is available to this session (a connected schema, data-source, or similar read-only tool) and permitted to this skill, query it before surfacing the question — the same answerable-from-a-source discipline already applied to static sources, extended to connected ones. Gate it on availability, not judgment: if such a tool is available, use it; if none is available (including because it is not permitted to this skill), ask the user as today. Keep it read-only — no writes, no state changes. If the answer is clear from evidence, record it in the spec with the evidence citation and move on — do not ask.
2. If evidence is insufficient, draft a recommended answer. Ground the recommendation in whatever evidence is available (prior decisions, conventions, stated goals, user's framing). State the recommendation, the rationale, and the alternatives considered.
3. Apply the YAGNI evidence test before surfacing. A decision that exists only for "completeness", "for future flexibility", "we might want to", "best practice", or symmetry with another feature is a YAGNI candidate per ../../references/yagni-rule.md. When no accepted evidence (user-described need, named direct dependency, existing code path, applicable regulation, documented incident/metric) supports the decision, the recommended answer is "defer this to the spec's ## Deferred (YAGNI) section with the reopening trigger named" — surfaced to the user with rationale like any other recommendation. When evidence does support the decision, apply the simpler-version test: is there a strictly simpler behavior that satisfies the same evidence? If yes, recommend the simpler behavior.
4. Surface to the user only if the decision genuinely needs their judgment. Present the recommendation, rationale, and alternatives. Allow the user to accept, amend, or redirect. Capture their answer verbatim in the spec.
5. Descend. Once a decision is settled, evaluate whether any dependent decisions are now resolvable from evidence (they often are). Repeat.

Keep the interview moving — do not stall on questions the evidence can answer. Do not batch every question upfront; ask as the tree unfolds, because later answers often resolve earlier uncertainties.

Routing implementation-level details

When settling a decision surfaces an implementation mechanic, classify it BEFORE writing the spec sentence and route it per mechanic-routing.md: a mechanic that changes observable behavior becomes a T# candidate, one already discoverable in the repo is cited as evidence on the D#, and anything else belongs to plan-implementation and is not settled here.

T-note capture discipline (in-message accumulator)

feature-technical-notes.md is not written during this step. Track candidates in-message as they are identified, so the user can redirect one before it reaches disk, and flush them in Step 5. The capture form, the two qualifying tests, and the flush procedure are all in t-note-protocol.md.

Step 5: Draft the Initial Feature Specification

Before drafting, invoke han-communication:readability-guidance to source the shared readability standard into your context, then apply it as you write the prose sections, holding the named audience: the stakeholder or reviewer who reads the spec for approval. The frame governs how a fact is said, never whether a required fact appears — keep the behavioral precision the spec depends on.

Write the files. The primary spec goes at the root of {folder}/; the companion artifacts go in {folder}/artifacts/ (create that subfolder if it does not already exist):

1. {folder}/feature-specification.md — use feature-specification-template.md. This is the primary behavioral spec covering: The template defines every section and carries the rule for what may and may not appear in the file. Three of its sections have behavior the template cannot express:

   • Visual Reference — write it only when the run received visual material. plan-work-items reads this table and the inline embed placements as its mapping source, so the exact heading text and the embed paths are a contract rather than a formatting choice.
   • Cut for Scope and Deferred (YAGNI) — both are lazily created. Omit either entirely when nothing qualifies. They sit adjacent and are the same shape, so each opens with one line saying what it is not. A cut carries no reopening trigger; a deferral does.

   For every behavior that embodies a non-obvious decision, append an inline parenthetical link to the decision in artifacts/decision-log.md, e.g. ([D4](artifacts/decision-log.md#d4-invite-expiration-window)). Link only non-obvious behaviors — not every sentence. "Non-obvious" means a reader would reasonably ask "why this and not something else?"

   For every spec sentence whose correct behavior relies on a captured T# note, append an inline parenthetical link to the note, e.g. ([T3](artifacts/feature-technical-notes.md#t3-ack-ordering)). Link only sentences where the mechanic changes observable behavior — never as a gratuitous "see also" link.

   Apply the spec-content rule from the operating principles to every sentence before writing it. If a draft sentence names a language primitive, file/line, function or class, library mechanic, implementation pattern, or internal flag, rewrite it behaviorally before it reaches disk. Route the implementation detail to the appropriate home per Step 4's routing rules.

2. {folder}/artifacts/decision-log.md — use decision-log-template.md. Do not classify decisions as full or trivial yet. Write every decision with the full structured fields, under ## Full decisions, and classify the whole set once in Step 8 after the review round returns. Two of the promotion signals, a driving finding and a linked technical note, cannot exist at draft time, so classifying now guarantees re-classification later. The D# counter is assigned here and stays stable through classification, so every spec inline link keeps resolving. The Driven by findings: field is — in this draft; it is populated in Step 7 when review findings reshape decisions.

3. {folder}/artifacts/team-findings.md — use team-findings-template.md. Write the header block; leave the findings list empty. F# entries are added in Step 7 after the review team returns.

4. {folder}/artifacts/feature-technical-notes.md — LAZILY created. Flush the in-message accumulator from Step 4 per t-note-protocol.md, which owns the re-validation, the T1..Tn assignment order, the fields each entry carries, and the inline links the flush adds to the spec and the decision log. When no candidate qualifies, the file is not created at all.

Technical details (specific files, libraries, data shapes) appear only under Evidence: in artifacts/decision-log.md or in Technical detail: entries in artifacts/feature-technical-notes.md — never as behavioral statements in feature-specification.md.

Step 5.5: Classify Feature Size

Before dispatching the review team, classify the feature. Default to small. Start the classification at small and only escalate to medium or large when the signals below clearly require it. When a signal is borderline, stay at the smaller band. Use the signals already in the draft spec:

• Small (default) — single subsystem, no cross-service integration, no auth/PII surface, no data migration, behavioral surface fits in one tab/page or one API call.
• Medium — two to three subsystems, optional integration, may touch UX or rollout, may have a small auth surface.
• Large — cross-service, security-sensitive, data ownership shifts, multiple new coordinations, or the user explicitly requests full team review.

This size drives the team-size cap in Step 6:

Size override. A non-empty $size wins: a band value skips the signal-based classification above, while dynamic forces it even when a config sets a default band. When $size is empty and a config supplies default-swarm-size (per config-rule.md), use that band and skip the classification. The team cap scales to whichever size wins. State the chosen size, the recommended specialists, and the reason in one short message before launching agents, naming which of the two config files supplied a band. If the user disagrees, accept their override of the size, the specialists, or both.