feat(aidd-product-manager): prefer PageSpace DOCUMENT pages for planning artifacts#215
feat(aidd-product-manager): prefer PageSpace DOCUMENT pages for planning artifacts#2152witstudios wants to merge 1 commit into
Conversation
When PageSpace MCP tools are connected, story maps, user journeys, and personas are now saved as DOCUMENT pages in the project's PageSpace drive. Falls back to $projectRoot/plan/story-map/ YAML files when PageSpace is unavailable. Non-breaking.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 580e80d8ac
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Pagespace available => create pages/documents in the project's Pagespace drive (preferred) | ||
| Story map, user journeys, and personas as DOCUMENT pages |
There was a problem hiding this comment.
Preserve journey YAML for the user-testing workflow
When PageSpace is connected, this branch replaces the filesystem output instead of supplementing it, so the documented /discover → /user-test journey.yaml workflow can no longer find its input. ai/skills/aidd-user-testing/SKILL.md:121-128 explicitly reads journeys from $projectRoot/plan/story-map/${journey-name}.yaml; either continue writing those YAML files or update the consumer to load DOCUMENT pages before making PageSpace the preferred destination.
Useful? React with 👍 / 👎.
| Pagespace available => create pages/documents in the project's Pagespace drive (preferred) | ||
| Story map, user journeys, and personas as DOCUMENT pages | ||
| Use list_pages to find an existing planning folder or create one | ||
| No Pagespace => save to $projectRoot/plan/story-map/ as YAML files |
There was a problem hiding this comment.
Update
/save to follow the PageSpace-first destination
When PageSpace is available and the user invokes /save, the new rule conflicts with the unchanged command contract at line 118, which still explicitly instructs the agent to export YAML into $projectRoot/plan/story-map/. Because /save is the operation that persists this state, that more specific instruction can bypass the newly preferred DOCUMENT-page behavior; make the command describe the same PageSpace-first/fallback branching.
Useful? React with 👍 / 👎.
Summary
mcp__pagespace__*tools are connected.list_pagesto find an existing planning folder or creates one.$projectRoot/plan/story-map/YAML files when PageSpace is unavailable — non-breaking.Why
PageSpace DOCUMENT pages are searchable, linkable, and visible in the workspace UI — a better home for living product artifacts than YAML files that only the AI ever reads. The filesystem fallback preserves existing behaviour for non-PageSpace projects.
Changes
ai/skills/aidd-product-manager/SKILL.md—FileLocationssection rewritten with PageSpace-first, filesystem-fallback branching