Public Template Recipe

Use public-template when you want a repository clients can inspect, fork, and adapt into their own reviewable sales or delivery pipeline.

Generate

node generator/create-index.mjs \
  --name "Acme Pipeline" \
  --slug acme-pipeline \
  --output ./acme-pipeline \
  --profile public-template \
  --owner "Acme Team" \
  --services github,slack,email,crm \
  --skip-install

What Gets Generated

• projects/ for opportunities, pilots, implementations, and active project context.
• partners/ for clients, prospects, vendors, delivery partners, and advisors.
• connectors/ for documenting external systems without storing secrets.
• pipeline/ for lightweight sales-stage review.
• notifications/ and email-groups/ for reviewable update templates and recipient groups.
• docs/ for public documentation and LLM-readable exports.
• repos/index.yaml for tracked repositories and source systems.
• workspaces/ records for structured context and ownership.
• mcp/ TypeScript MCP starter files for read-only context.
• evals/ smoke tests for prompt, retrieval, and output-format changes.

First Validation

cd acme-pipeline
npm install
npm run check

Next Steps

• Replace example project and partner pages with real reviewable records.
• Add connector pages only for systems the team can test.
• Keep notification groups small until the preview and test-send path is configured.
• Run checks before sharing the repository with a client reviewer.