/seed — Load the Current Intent Seed into Session Memory

What It Does

A "seed" is a short, confirmed written record of what the person is building, why, and what success looks like from a real user's side — the thing /align creates once intent is confirmed, and the thing deploy-alignment-guardian checks finished work against. /seed is the loader: it finds the current one for this project, prints its core intent statements to chat, and makes sure the rest of the session is steered by that stated intent instead of the agent's own guess.

When invoked, this skill:

1. Finds the seed (see "Where seeds live" below)
2. Prints its core intent statements — what it makes possible, what success looks like, what's still open — to chat, quoted from the file, not paraphrased into something looser
3. If nothing is found, says so plainly and offers to run /align to create one

Where seeds live

In order:

1. A configured seedPath (or SEED_PATH) pointing at a specific file, if one is set for this project.
2. The most recently modified .md file in the folder alignment-harness records seeds prints (defaults to docs/intent/seeds/ in the current project if the harness CLI isn't set up).
3. If neither exists: there is no current seed. Say so — don't invent one, don't treat an unrelated doc as if it were a seed.

When to Use

Invoke this skill when:

• Starting alignment work on a project or initiative and you want to confirm what's already been established before assuming anything
• Another skill says "no seed exists, run /seed (or /align) first" — deploy-alignment-guardian does exactly this before it will start monitoring
• You want to check whether your current plan still matches what was confirmed, before building further on top of it

How to Invoke

# Primary way — via skill command
/seed

# Or read the raw seed document directly, once you know its path
cat "$(alignment-harness records seeds)"/*.md

If no seed exists yet

Say so in plain terms — something like: "There's no confirmed intent seed for this project yet, so I don't have a written record of what you're building and why to check my work against. Want me to run /align to work that out with you and write one?" Then, on a yes, hand off to /align, which is the skill that confirms intent and creates the seed (see its own SKILL.md for the format — "What this makes possible", "What success looks like", frontmatter status: aligned).

Never fabricate a seed's contents to fill the gap, and never treat a plan, a proposal, or a README as if it were a confirmed seed just because nothing else is available.

Related Skills

• /align — confirms intent with the person and creates the seed this skill loads
• /decompose — converts a confirmed seed into an observable, testable plan
• deploy-alignment-guardian — reads the current seed and watches for drift against it once deployed
• /close — offers to save a session's clarified intent as a new (or updated) seed at the end of a session