flow

Decision 0007 · Accepted

Official Flow product identity
in PRODUCT.md

Earlier product copy centered flow-skills as a skill collection.

Status
Accepted
Built from:
da88c48

Status: accepted (2026-10-27). Amended by 0049 (principle 3 becomes human-directed, agent-executed).

Context

Earlier product copy centered flow-skills as a skill collection. October 24–27 discussions (Flow Starter, Flow Factory, simplified catalog) clarified that Flow is a product-minded methodology for developing software with AI agents—not only portable coding skills. Several earlier statements (lightweight methodology, preserve intent, documented way of working, intent-to-verified-value, improve through use) remain stronger than skill-first framing.

Decision

  • PRODUCT.md owns official Flow identity — tagline, mission, definition, experience, seven principles, success measure, strategic chain, ecosystem boundaries, and dogfooding rule.
  • flow-skills section — catalog, install, scope, and catalog-alignment guidance stay in the same file under “This repository: flow-skills” so adopters still find distribution facts in one place.
  • Reserved naming — “Agentic product factory” language applies to Flow Factory, not Flow or flow-skills.
  • Human-led, agent-assisted — explicit distinction: agents take more execution; humans retain product direction and consequential decisions.
  • Before adding skills — evaluate against the strategic chain and the catalog-alignment table; prefer simplification over growth.

Consequences

  • docs/principles.md and docs/methodology.md remain elaboration and optional practice; they do not supersede the seven principles in PRODUCT.md.
  • Future specs and skills should cite PRODUCT.md when scope or identity is in question.

References

Jump to, or try a question