Imported from ismailsaleekh/vibe-engineer (.vibe/work/WC-B1/vs-29-baseline/post/files/import-pi/AGENTS.md). Install upstream with npx skills add ismailsaleekh/vibe-engineer --skill import-pi. Copyright stays with the author.

wcb1-baseline — Project Context (AGENTS.md)

Bootstrap context generated by 'vibe-engineer create/import'. This is sparse, provenance-labeled setup context — NOT a product plan. Every load-bearing statement carries a DL-17 provenance label.

Setup facts

• Project name: 'wcb1-baseline' (slug 'wcb1-baseline') — provenance: normalized_from_user (create/import naming value)
• Selected agentic harness: 'pi' (Pi Coding Agent) — provenance: harness_default (selected harness adapter boundary)
• Adapter capability version: 'pi-adapter-capability-matrix/v1' — provenance: harness_default (selected harness generated-file manifest)
• Generated-file manifest version: 'pi-generated-file-manifest/v1' — provenance: harness_default (selected harness generated-file manifest)

Brief status

Brief status: 'skipped' (placeholder — no user-provided brief). High-level product context is intentionally incomplete ('needs_user_context').

High-level context (intentional placeholder)

• Goals: unknown — provenance: unknown (No project brief was provided.)
• Constraints: unknown — provenance: unknown (No project brief was provided.)
• Non-goals: unknown — provenance: unknown (No project brief was provided.)
• Audience/users: unknown — provenance: unknown (No project brief was provided.)
• Integrations: unknown — provenance: unknown (No project brief was provided.)

Unknowns

• Project purpose / desired outcome is unknown (no brief provided). — provenance: unknown
• Goals, constraints, non-goals, risks, and acceptance criteria are unknown. — provenance: unknown
• Intended audience/users are unknown. — provenance: unknown
• Domain-specific context is unknown. — provenance: unknown

Next step (advisory)

Project foundation: Use the project skill with /skill:project to establish and evolve the project foundation conversationally. — provenance: harness_default (DL-29). Concrete task request: Run the brainstorm skill with /skill:brainstorm and several sentences describing the project to create the initial Work Brief and project context. — provenance: harness_default (task discovery).

Provenance map

{
  "projectName": {
    "label": "normalized_from_user",
    "source": "create/import naming value"
  },
  "projectSlug": {
    "label": "normalized_from_user",
    "source": "create/import naming value"
  },
  "selectedHarness": {
    "label": "harness_default",
    "source": "selected harness adapter boundary; supported harnesses: pi, claude-code, codex"
  },
  "briefSummary": {
    "label": "placeholder",
    "source": "no user-provided brief"
  },
  "goals": {
    "label": "unknown",
    "source": "no brief provided"
  },
  "projectInstruction": {
    "label": "harness_default",
    "source": "DL-29 missing-foundation instruction (the one project skill)"
  },
  "brainstormInstruction": {
    "label": "harness_default",
    "source": "task-discovery route (DL-29: a concrete task request still routes to discovery)"
  }
}

Invariants (harness_default)

• Product/package/CLI name: vibe-engineer.
• Six skills: brainstorm, grill-me, task, plan, build, ship.
• Artifact flow: raw intent → Work Brief → Implementation Plan → Build Result → Ship Packet.
• Anti-overdesign (DL-17): no roadmap, schema, domain model, architecture, users, integrations, or workflow is inferred from a sparse/skipped brief.