feat(aidd-fix): add PageSpace MCP task status integration#213
feat(aidd-fix): add PageSpace MCP task status integration#2132witstudios wants to merge 1 commit into
Conversation
Step 1 now reads the task from the PageSpace epic TASK_LIST first (via read_page) if MCP tools are connected, falling back to $projectRoot/tasks/. Adds a step to set the task in_progress on confirmation. Step 2 creates a PageSpace TASK_LIST (not just a filesystem epic) when MCP is available. Step 6 marks the task completed and captures root cause + prevention rule into PageSpace memory on commit. Non-breaking fallback to filesystem when no MCP.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c525ec3726
ℹ️ 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".
| 3. PageSpace available => set the task to in_progress (update_task) once the issue is confirmed | ||
| 4. Reproduce or reason through the issue to confirm it exists |
There was a problem hiding this comment.
Because this skill requires steps to execute in order, PageSpace's update_task runs before step 4 confirms the issue. For a false or already-resolved bug report, step 5 then stops the workflow without restoring the status, leaving the task incorrectly marked in_progress. Reproduce or reason through the issue before updating its status.
Useful? React with 👍 / 👎.
| documentRequirement(confirmedIssue) => requirement { | ||
| 1. Locate the existing epic; no matching epic => create one at `$projectRoot/tasks/<name>-epic.md` using /task | ||
| 2. Add a requirement in **"Given X, should Y"** format describing the correct observable behavior | ||
| 1. Locate the existing epic/task; none => create one with /task (a PageSpace TASK_LIST when the MCP tools are connected, else `$projectRoot/tasks/<name>-epic.md`) |
There was a problem hiding this comment.
When PageSpace is connected and no task exists, /task cannot provide the promised TASK_LIST: ai/skills/aidd-task-creator/SKILL.md:10 explicitly stores tasks under $projectRoot/tasks, and that skill contains no PageSpace branch. This creates a filesystem epic while subsequent steps attempt update_task against a nonexistent PageSpace task, so the new integration fails for exactly the missing-task case. Invoke the appropriate PageSpace creation operation here or add PageSpace support to /task first.
Useful? React with 👍 / 👎.
1 participant
Summary
read_page) ifmcp__pagespace__*tools are connected; falls back to$projectRoot/tasks/.in_progressviaupdate_taskonce the issue is confirmed./task) instead of a filesystem epic file when MCP is available.completedand captures root cause + prevention rule into PageSpace memory (a note page + Memory Index line).Why
When using PageSpace as the task board, the fix workflow should close the loop: read the task from PageSpace, flip it in_progress while working, and mark it done with a memory capture on commit — so the board always reflects reality without manual updates.
Changes
ai/skills/aidd-fix/SKILL.md— Steps 1, 2, and 6 updated with PageSpace-aware branches