You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .agents/skills/project-manager/SKILL.md
+27-19Lines changed: 27 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,11 @@
1
1
---
2
2
name: project-manager
3
-
description: "Manage GitHub issues and the GitHub Project board for this repository, while keeping the local tracker in sync. Use when the user wants to capture freeform requirements as issues, flesh out issue descriptions from repo or upstream research, triage Priority/Size/Workflow/Status, add issues or PRs to project 7, or reconcile GitHub state with `.local/work-items.yaml`."
3
+
description: "Manage GitHub issues and the GitHub Project board for the current repository, while keeping the local tracker in sync. Use when the user wants to capture freeform requirements as issues, flesh out issue descriptions from repo or upstream research, triage Priority/Size/Workflow/Status, add issues or PRs to the repo's configured project board, or reconcile GitHub state with `.local/work-items.yaml`."
4
4
---
5
5
6
6
# Project Manager
7
7
8
-
Use this skill for repo-specific project management on [OpenClaw Codex App Server Project](https://github.com/orgs/pwrdrvr/projects/7).
8
+
Use this skill for repo-local project management.
9
9
10
10
## Automation Preference
11
11
@@ -19,14 +19,21 @@ Use this skill for repo-specific project management on [OpenClaw Codex App Serve
19
19
- Treat `.local/work-items.yaml` as a derived repo-local cross-reference map that can be regenerated from the project board.
20
20
- Put temporary issue writeups only in `.local/issue-drafts/`.
21
21
- Do not create parallel scratch directories or alternate tracker files for the same purpose.
- Use `gh issue create`, `gh issue edit`, and `gh issue comment`.
52
59
- Keep titles short and imperative, usually starting with `Plugin:`.
53
60
54
-
4. Add the issue or PR to project `7`.
61
+
4. Add the issue or PR to the configured project board.
55
62
56
-
- Use `gh project item-add 7 --owner pwrdrvr --url <issue-or-pr-url>`.
63
+
- Read the configured project number and owner from `.agents/project-manager.config.json`.
64
+
- Use `gh project item-add <project-number> --owner <project-owner> --url <issue-or-pr-url>`.
57
65
- For issues, set `Status`, `Priority`, `Size`, and `Workflow`.
58
66
- For PRs, usually set `Status` and `Workflow`; `Priority` and `Size` are issue-planning fields unless there is a specific reason to set them on the PR item.
59
67
@@ -91,17 +99,17 @@ Start by discovering current project field ids instead of assuming they never ch
- Verify the repo slug before issue commands. The canonical repo is `pwrdrvr/openclaw-codex-app-server`; older shorthand like `pwrdrvr/openclaw-app-server` is wrong and will make `gh issue ...` fail.
123
+
- Verify the repo slug before issue commands. Treat `.agents/project-manager.config.json` as canonical when it is present.
116
124
-`gh project item-edit` needs opaque ids for the project, item, field, and single-select option. Always discover them with `gh project view ...` and `gh project field-list ...` instead of assuming cached ids still match.
117
125
- GitHub Projects custom views are not well-supported by `gh` or GraphQL mutations. Reading views works, but creating/editing/copying views is still better done in the web UI or browser automation. `gh project copy` does not carry over custom views.
118
-
-`.local/work-items.yaml` is currently issue-only. Add PRs to project `7`, but do not expect `pnpm project:sync` to mirror PR items into the local tracker.
126
+
-`.local/work-items.yaml` is currently issue-only. Add PRs to the project board, but do not expect `pnpm project:sync` to mirror PR items into the local tracker.
119
127
-`.local/issue-drafts/<nn>-<slug>.md` filenames are local scratch ids, not GitHub issue numbers. Keep them stable enough to reuse, but do not try to force them to match the eventual GitHub issue number.
short_description: "Manage issues, board, and local tracker"
4
-
default_prompt: "Use $project-manager to capture requirements into GitHub issues, keep project 7 in sync, and update the local .local tracker for this repo."
4
+
default_prompt: "Use $project-manager to capture requirements into GitHub issues, keep the configured project board in sync, and update the local .local tracker for this repo."
0 commit comments