E11 Foundry

Appearance

Phase 1 — Analysis ​

Pre-PRD discovery. The output of this phase is enough context for PM to start a PRD without guessing.

Owner: Analyst (agent-skill e11-agent-analyst). The Tech Writer also lives in this phase for doc-first work.

Workflows in this phase ​

CodeWorkflowPurposeOutput
[CB]e11-product-briefConsolidated brief — Create / Update / Validate in one skill, stakes-calibrated{planning_artifacts}/briefs/brief-<project>-<date>/brief.md
[PF]e11-prfaqWorking-backwards PRFAQ — press release + customer FAQ + internal FAQ + verdict{planning_artifacts}/prfaq-<project>.md
[MR]e11-market-researchMarket analysis, competitive landscape, customer needs, trends{planning_artifacts}/research/market-*.md
[DR]e11-domain-researchIndustry deep dive, terminology, subject-matter expertise{planning_artifacts}/research/domain-*.md
[TR]e11-technical-researchFeasibility + architecture options — alloy-first, web only for non-E11 tech{planning_artifacts}/research/technical-*.md

Also from here (anytime, Analyst-owned): [DP] e11-document-project and [GPC] e11-generate-project-context — see the phase map.

How the analysis skills are shaped ​

  • The brief is one skill with three intents. e11-create-product-brief still answers as a deprecated shim forwarding to e11-product-brief (Create); it disappears next major release.
  • Fast path vs coaching path. The brief reads stakes early and offers a batched-questions fast path (draft with [ASSUMPTION] tags) or section-by-section coaching. Ceremony scales with stakes, not habit.
  • PRFAQ — a customer-first stress test before you invest in a PRD (deep page). Pair with e11-forge-idea (deep page) when the idea itself is still soft.
  • The research trio gained a customization surface — e.g. technical research's alloy-first pass is the e11_platform_alloy_first gate in its customize.toml (default on).

Standard flow ​

  1. [CB] Product Brief if you don't have one. The brief is the seed PM needs for [PR].
  2. [TR] Technical Research for any major tech decision you'd like surfaced before the PRD. Output keeps "From alloy" and "From the web" partitioned.
  3. [MR] / [DR] when success depends on non-E11 industry knowledge. Skip for fully internal-ops projects.
  4. [PF] PRFAQ when the concept needs a go/no-go verdict before the PRD investment.

When to detour ​

  • No idea, just a problem. Start with e11-discovery (deep page) or [TR]/[MR] — research informs the brief.
  • Idea too soft for a brief. e11-forge-idea pressure-tests it conversationally first.
  • Brownfield codebase. Run [DP] / [GPC] before research; you'll waste cycles otherwise.
  • You already have a brief from elsewhere. Run [CB] with Validate intent to bring it up to standard, then go straight to PM [PR].

Hand-off ​

Output of Phase 1 → input to Phase 2 (Planning). PM's [PR] (Create) reads the brief and any relevant research artifacts; e11-spec-flow can also distill a finished brief straight into a spec kernel for small efforts.

Source ​

Workflow SKILL files:

Proprietary to Engineering11 LLC.

Tools to build at AI speed and volume.