# Plastic — Project Agent Instructions

> Full conventions: see `~/.plastic/PLASTIC.md` (the global conventions contract).
> This file covers project-scoped rules only.

## Your Role

You are working on this project as part of a strategic intent. Your governing intent is tracked in the global Plastic store at `~/.plastic/store/`.

## Tools

Plastic detects the tools it can use to work faster on this project: QMD (search this
project's intent store instead of grep), and Serena or Enola (symbolic code navigation
instead of grep). None is required. Whichever are present, their readiness is checked every
time this project loads (`doctor --store <slug>`), so working through Plastic on this project
means preferring a detected tool's own search or navigation over a generic file scan.

## How to Work

1. **Check active tactical intents** in `.plastic/store/` — these are your current tasks
2. **Create new tactical intents** when you discover sub-work needed
3. **Use [[ID]] wikilinks** to link intents to each other
4. **Use [[global:ID]]** to link back to the governing strategic intent
5. **Auto-commit** all intent changes in this project's git repo

## Intent Lifecycle — What→Why→How→Exec

State is derived from filesystem conventions, not frontmatter fields:

| Convention | Signal |
|---|---|
| `## Context` has content | Intent is permanent (developed, actionable) |
| `## Outcome` has content | Intent is done |

Sections map to the lifecycle:
- **## Intent** — What (the desire)
- **## Context** — Why (background + ### Decisions)
- **## Outcome** — Exec (the result; How's deliverables are the `plan.md`, `actions/`, and `checklist.md` files)
- **## Insights** — observations across all stages, raw material for future intents

Active/Future/Completed placement is managed in INDEX.md, not in frontmatter.

## Creating Tactical Intents

Create through the `plastic-intent-creating` skill, which scaffolds with one call:
`ruby ~/.plastic/scripts/new-intent --store .plastic/store --intent "<one-line>" --slug <slug> [--sources <governing-id>]`.
It allocates the Folgezettel ID, creates `.plastic/store/ID--slug/ID--slug.md` born
complete, and wires the links. Never hand-author the files: the write-time create gate
rejects an incomplete or malformed intent file.

## Lifecycle Skills

Plastic has its own lifecycle skills. When a Plastic skill exists for the current phase, use it instead of any external skill (superpowers, superpowers-ruby, etc.).

| Phase | Skill | Produces |
|-------|-------|----------|
| What | `plastic-intent-creating` | Intent file |
| Why | `plastic-intent-brainstorming` | Enriched `## Context` + `### Decisions` |
| Why | `plastic-intent-speccing` | `spec.md` |
| Why | `plastic-intent-researching` | `resources/*.md` |
| Why | `plastic-intent-grilling` | Deep interrogation |
| How | `plastic-intent-planning` | `plan.md`, `checklist.md`, `actions/` |
| Exec | `plastic-intent-executing` | Code + `outcome.md` |
| Done | `plastic-intent-ending` | Lifecycle transition |

**Artifact convention:** ALL lifecycle artifacts go to the active intent directory (`store/{id}--{slug}/`). Never write specs to `docs/superpowers/specs/` or plans to `docs/superpowers/plans/`.

## When You're Done

When this project satisfies the governing intent's goal, report back. The orchestrator will complete the strategic intent.