Skip to content

feat(aidd-product-manager): prefer PageSpace DOCUMENT pages for planning artifacts #215

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
2witstudios wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat(aidd-product-manager): prefer PageSpace DOCUMENT pages for planning artifacts #215

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions ai/skills/aidd-product-manager/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -100,10 +100,13 @@ CrudOperations {
}

FileLocations {
Story maps and user journeys are saved to $projectRoot/plan/story-map/ as YAML files
Story map file: $projectRoot/plan/story-map/story-map.yaml
User journey files: $projectRoot/plan/story-map/${journey-name}.yaml
Personas: $projectRoot/plan/story-map/personas.yaml
Pagespace available => create pages/documents in the project's Pagespace drive (preferred)
Story map, user journeys, and personas as DOCUMENT pages
Comment on lines +103 to +104

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 12, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge 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 👍 / 👎.

Use list_pages to find an existing planning folder or create one
No Pagespace => save to $projectRoot/plan/story-map/ as YAML files
Comment on lines +103 to +106

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 12, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge 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 👍 / 👎.

Story map file: $projectRoot/plan/story-map/story-map.yaml
User journey files: $projectRoot/plan/story-map/${journey-name}.yaml
Personas: $projectRoot/plan/story-map/personas.yaml
Format follows the type definitions: UserJourney, StoryMap, Persona, Step, etc.
}

Expand Down
Loading