Sign in with your Personalisation Hub account to open the board and the help-centre editor.
or use your email and password
Checking sign-in…
Sign in with your Personalisation Hub account to open the board and the help-centre editor.
Checking sign-in…
🎤 Listening — tap the mic again when you're done.
A short title and best-guess area are generated from what you write — Claude sets the final ones once this ticket is actually looked at.
Optional — groups this under a shared heading on the board.
Repo-root-relative, no trailing slash. This is what a Routine session's patchFiles get placed under — see root CLAUDE.md → "Linking a new project to GitHub".
Optional — groups this under a shared heading on the board.
Optional — the release this project ships in. Create one on the Releases page first if it doesn't exist yet.
Repo-root-relative, no trailing slash — see root CLAUDE.md → "Linking a new project to GitHub".
Copies this concept's README and requirements onto the new project and marks the concept promoted — it stays on this page afterward, read-only.
Visible and editable from both projects' Docs pages — this is the shared, maintained contract between them.
Lowercase letters, numbers and hyphens only — must be unique. Can't be changed once a skill is created.
Informational only — which team maintains and optimises this skill. Anyone with editor access can still improve any skill.
At least one file. Each is a path (e.g. SKILL.md or references/tokens.md) and its full content.
Paste one requirement per paragraph (blank line between each). Preview how they'd cluster into build batches before creating anything.
Effort/priority (cwehxSMZv8noJQv5kB22): concrete signals for the "Feed in requirements" clustering preview to sort and batch on — set here to override its automatic guess, or leave Unset to keep using that guess.
For a fix that's just a live data/config change with no code to push — e.g. a Firestore-only edit — nothing ever needs to reach GitHub. Check this and, once tested, the card can move straight from Ready for Testing to Deployed / Main Branch (Live), skipping Approved for Deployment and Deploy to Main entirely.
🎤 Listening — tap the mic again when you're done.
This ticket is locked while its work is in progress — you can read the thread, but not add to it yet.
🎤 Listening — tap the mic again when you're done.
Groups this project on the board.
The release this project ships in. When set, approved FAQ updates from this project's tickets wait for the release to be marked live, then go live together. Create a release on the Releases page first.
One or two sentences on what this project covers. Shown to AI agents in list_projects so a loose reference ("the FAQ backlog") maps to the right project.
The join between this project and its folder in rob_ph_demos — read by projectFolderOf() to place a Routine session's folder-relative patchFiles correctly. Repo-root-relative, no trailing slash.
Keep in sync with this project's README.md in the repo.
Keep in sync with this project's REQUIREMENTS.md in the repo.
Any other technical document for this project — a spec, a design doc, etc.
Extra context sent to Claude with every Routine run for this project. Optional.
Flags linked FAQ articles for review when a ticket for this project merges to main.
A shared contract document with another project.
| Type | Area | Ticket | Version | Date | |
|---|---|---|---|---|---|
No archived tickets match these filters.
| Project | Active items | Archived |
|---|
No archived projects.
Part of this article's formatting isn't supported by the editor and was simplified on load. Compare with View live before saving.
Anyone listed here can sign in to the PH Agent Console — with Google, or with an email and password — and connect their own AI agent to it. Editor can change the board; viewer can only read it; admin can also manage this list. Turning Agent off leaves someone's browser access untouched but disconnects their agent immediately.
Google accounts work as soon as they're added. For someone without one, use Send sign-in setup on their row — it creates their login and emails them a link to choose a password.
Add the PH Agent Console to Claude (or any MCP client) as a remote MCP server. It will open a sign-in page — use the same account you're signed in with here. Your agent never sees your password, and everything it files or comments is recorded under your email.
https://backlog-tracker-e4ed2.web.app/mcp
In Claude Code: claude mcp add --transport http ph-console https://backlog-tracker-e4ed2.web.app/mcp
A Google Analytics measurement ID (e.g. G-XXXXXXXXXX) or a Google Tag Manager container ID (e.g. GTM-XXXXXXX) — set here once, it gets appended to every customer-facing FAQ page (the front page, category pages, article pages, and search), not just one. Leave blank to track nothing.
Settings for the mic button on New backlog item and every comment box. Kept in this browser only — nothing here is shared with teammates.
Whole projects that have been archived off the board — restore one to bring it back.
Drag any row to re-order it. That order is what visitors see on the help centre.
Nothing here yet.
A shared library any team member's AI agent can read over MCP — packaged instructions like this console's own front-end design skill. Anyone signed in can read a skill; adding, editing or removing one needs editor access.
No skills yet.
Early-stage ideas that need more shape before they become an official project on the board. Each concept keeps its own README, requirements and discussion thread — pick up the conversation any time, then promote it to a real project once its structure is agreed.
No concepts yet — capture an idea with "+ New concept" before it needs to be a full project.
What this concept is and why — carried across verbatim if it's promoted to a project.
A link to a non-live mockup or clickable prototype of this idea (https only) — not a live site or wired-up code.
Update these incrementally as the idea develops — saving here never touches the README above.
Retained across sessions — pick the conversation back up any time.
🎤 Listening — tap the mic again when you're done.
Carries this concept's README and requirements across so nothing is re-keyed, and assigns it a release. This concept then becomes read-only — the project's own Docs page takes over from here.
Only while still active — a promoted concept is kept as the record of where its project's README/requirements came from.
A release bundles projects so their approved FAQ updates go live on the help centre together, the moment the release is marked live. Marking a release live can't be undone.
| Release | Version | Status | Projects | Created |
|---|
No releases yet.
Comments
🎤 Listening — tap the mic again when you're done.