Seed (structured intent)

The seed is the factory’s first input. If it is vague, the model fills specification gaps arbitrarily—and you ship wrong software at high speed.

A strong seed typically includes: functional intent, non-functional constraints (performance, security, scale), code conventions (explicit, not assumed), domain model (entities and boundaries), and tech stack choices.

Seeds can be PRDs, RFCs, constitution files (CLAUDE.md / AGENTS.md), user stories, formal protocol specs with external validators, screenshots, or even an existing working codebase treated as an executable specification.

EasySpecs is built to provide exactly this: a systematic way to produce, structure, and evolve the seed—discovery, SRS-style living requirements, dimensions, and drift control—so your factory’s first input is explicit and maintained, not a vague brief the model must invent.

See also: Seed manufacturing system, Requirements gathering (for agent factories), Spec-driven development, Context engineering.