plastic-intent-creating

name	plastic-intent-creating
description	Use when new work begins, the user expresses a new goal, says "new intent", or no active intent exists for the current task. Creates intents in the global store (~/.plastic/store/) or in a project's store (~/.plastic/projects/{slug}/store/) depending on context.
user-invocable	true

Creating an Intent

When to Use

• User starts new work ("build X", "fix Y", "research Z")
• No active intent matches the current task
• User explicitly says "new intent" or "create intent"
• An agent discovers work needed during implementation

Determine Tier

Global intent (strategic): created when working outside a registered project, or when the user expresses a high-level goal. Stored in ~/.plastic/store/.

Project intent (tactical): created when working inside a registered project directory. Stored in ~/.plastic/projects/{slug}/store/. Automatically linked to the project's governing intent.

Detection logic:

1. Read ~/.plastic/projects.yml
2. CWD match: Match CWD against registered project paths
   • If CWD is inside a registered project → project intent (tactical)
3. Explicit mention: User mentions an existing project by name ("add this to reddit-kb", "new intent for plastic")
   • Look up project in projects.yml by slug
   • If found → project intent (tactical) in that project's store at ~/.plastic/projects/{slug}/store/
   • Agent changes working directory to the project path for execution
4. No match: CWD is not in a project AND no project mentioned
   • → global intent (strategic) in ~/.plastic/store/

When creating a tactical intent in a project store:

• Read the project's AGENTS.md for project context and decisions
• Link back to the project's governing intent (from projects.yml parent field) via sources (the project genuinely is formed from its founding intent, a true formative edge, reciprocated on the founding intent's chain)
• Add [[global:<parent_ID>]] backlink in ## Links
• The intent's Folgezettel ID is scoped to the project store (run folgezettel-id against the project's store at ~/.plastic/projects/{slug}/store/)

Workflow

1. Determine Store Location

• Global: ~/.plastic/store/
• Project: ~/.plastic/projects/{slug}/store/

1b. Check for a Duplicate or Predecessor (QMD-first)

QMD-first (when available): before scanning the store with grep/Read, run ruby ~/.plastic/scripts/qmd-sync search "<terms>" to surface candidate, prior, or duplicate intents, then open the authoritative intent file for any hit you act on. The command is a no-op when QMD is absent, so fall back to the existing INDEX.md / file scan. Do this before allocating the id so a near-duplicate can be reused and a true predecessor can be set in --sources.

2. Decide Branch vs Root

Decide this BEFORE scaffolding, because it sets whether you pass --parent. Having a "parent" in mind does NOT automatically mean branch. Choose by meaning:

• Branch (14a, 14b): a sub-task, refinement, or direct continuation. It only makes sense as part of the parent's work. Pass --parent <parent_id>.
• Root (15, 16): an independent thought. Two cases, decided by ORIGIN:
  • Created from another intent (it emerged from that intent's lifecycle): make it a root and set --sources <ascendant_id>. sources is reserved for true created-from / direct-ascendant provenance (D1).
  • Merely related to / inspired by another intent (it did NOT come out of that intent's lifecycle): carry NO --sources. Record the relation on the PREDECESSOR's chain instead (the related-but-not-spawned rule); the ## Links section follows from that edge, you do not write it by hand.
• Rule of thumb: if the intent could exist without its parent, make it a root; only set --sources when it was genuinely created from / emerged from that intent's lifecycle. Topic similarity alone is not a sources edge.

When a branch intent exists because a late ruling arrived AFTER its parent was already completed (the owner's late-ruling rule), the parent is restored to v1 via scripts/restore-intent-v1, never by a hand-run git checkout/revert. See PLASTIC.md > Terminal immutability for the rule and the tool.

## Links is a DERIVED view of sources/chain. Never hand-write a ## Links line; add the frontmatter edge and reproject. Links are decided by context influence (a chain edge has a high bar: the candidate's context must materially help deliver this intent), not by shared files or a similarity score. To gather candidates with their context and record an edge, use the plastic-intent-linking skill and scripts/link-suggest.

3. Determine Intent Properties

Ask or infer from context:

• intent: one-line description
• slug: short hyphenated handle for the directory name
• author: human | claude-code | other agent name
• sources: the direct ascendant(s) this intent was created from / emerged from the lifecycle of (formation, not topic similarity), e.g., 4a1. For a project intent, include the governing intent's id. A branch's structural parent is ALSO recorded in sources (the ID carries it for the human/paper tree, sources carries it for software), which new-intent does automatically (see new-intent:126).
• tags: freeform list (use project-<name> for project membership)

chain carries what this intent spawns AND related-but-not-spawned successors it leads to; it starts empty and is populated later. See docs/concepts/how-plastic-sources-and-chains-intents.md for the full model. Place the intent in ## Active or ## Future in INDEX.md (status is convention-derived, not a frontmatter field).

4. Scaffold via new-intent (single call)

Delegate id allocation, directory and file creation, the born-complete intent file, the sentinel placeholder lifecycle files, the reciprocal file links, and self-validation to one new-intent invocation. Do NOT hand-author any of these files.

"${CLAUDE_PLUGIN_ROOT}/scripts/new-intent" \
  --store "<STORE>" --intent "<one-line>" --slug "<slug>" \
  [--parent "<parent_id>"] [--author "<author>"] \
  [--sources "id,id"] [--tags "project-<slug>,tag"]

new-intent allocates the Folgezettel id (root, or a branch of --parent), creates <STORE>/<id>--<slug>/ plus actions/ and resources/, renders the born-complete <id>--<slug>.md from the intent template, writes the sentinel placeholder spec.md/plan.md/checklist.md/outcome.md (each marked <!-- plastic:placeholder --> so no stage detector reads them as reached), wires the reciprocal [[id]] links, and self-validates (frontmatter plus the sanctioned ## sections). It prints the created directory path and exits 0.

It does NOT touch INDEX.md, git, or project creation: those stay in this skill (steps 6 to 9 below).

If new-intent exits non-zero, read the stderr report and fix the inputs (slug, intent, sources). Do not commit or announce an intent that did not scaffold cleanly, and do not work around the failure by hand-writing the files.

6. If Implementation Intent Spawns a Project

When the user says "start building" or the plan calls for a new project, invoke the plastic-project-creating skill; it owns project directory creation, AGENTS.md population, projects.yml registration, store provisioning, and the auto-commit of both stores. Add project-<slug> to this intent's tags array either before invoking it or as part of that skill's handoff.

7. Update INDEX.md

• Global intents: update ~/.plastic/INDEX.md
• Project intents: no global INDEX.md change (tactical intents are project-scoped)

Add to ## Active (or ## Future) and appropriate cluster.

8. Auto-commit

cd <store-root> && git add . && git commit -m "feat: create intent ID - [name]"

9. Announce

"Created intent ID - [name]. Placed in: [Active|Future]. Store: [global|project:|local]."

References

• Read references/lifecycle.md for the full What→Why→How→Exec stage detail, filesystem-as-schema conventions, and creating-intent step-by-step
• Read references/wikilinks.md for the wikilink syntax table when adding ## Links to intents