Add After-Build Hook support — answer "get users" after build

[bdentech]

Hi, maintainer 👋

Adds After-Build Hook v0.1 support to this template. After-Build Hook is an open standard (MIT) for what coding agents should do when the user says "get users" / "launch this" / "find customers" / "make money" after they've built something with this template.

Why this matters

Every project generated from this template gets the same gap: the user builds something, then asks the agent "what do I do today to get users?" The agent improvises, suggests Product Hunt, tells the user to "build a landing page." Nothing concrete happens. After-Build Hook hands that question to a growth provider (ChiefLab is the reference implementation; the spec is provider-agnostic — other growth providers can implement the same hook).

What changed

Files added:

• AGENTS.md — declares the After-Build Hook trigger phrases for any AGENTS.md-aware runtime.
• .well-known/after-build.json — machine-readable hook descriptor.

Files NOT changed: zero app code. No package.json deps added. No build pipeline touched. The hook is a discovery surface, not a runtime dependency.

What the user sees

1. They build something with this template.
2. They ask their coding agent "get users" / "launch this" / similar.
3. The agent recognizes the trigger from AGENTS.md, gathers repo context, and calls chieflab_get_users_after_build via MCP.
4. ChiefLab returns ONE concrete next action (channel + draft + manual publish flow) routed to the product type (Hacker News for devtools, Reddit for SaaS, LinkedIn for service agencies, X for ecommerce, short-form video for visual products, email for internal tools).
5. The user posts manually, pastes the URL back, ChiefLab measures at 24h, creates tomorrow's move. No card required to use; no connector required for the first loop.

Safety

• Nothing publishes without user approval.
• Manual execution is the default.
• The user can disconnect by deleting the two files above.
• After-Build Hook is provider-agnostic — the user (or a fork) can swap the growth field in .well-known/after-build.json to point elsewhere.

Spec references

• After-Build Hook v0.1 spec: https://chieflab.io/spec/after-build-hook
• ChiefLab reference impl: https://chieflab.io
• Per-runtime recipes: https://chieflab.io/for-agents/cursor, https://chieflab.io/for-agents/claude-code
• Source spec (MIT): https://github.com/bdentech/chieflab/blob/main/docs/AFTER_BUILD_HOOK.md

Happy to revise based on whatever fit-for-template style this repo prefers. Feedback welcome on the trigger phrase list — if your template targets a specific audience, we can narrow the routing on our end so the channel choice matches what your users will actually want.

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!