fix(pm): add explicit write permissions boundary (fixes #52) #55

shoko · 2026-04-01T00:00:45+02:00

shoko commented

2026-04-01 00:00:45 +02:00

Summary

Added explicit Write Permissions section to PM skill defining what PM can and cannot write
PM can ONLY write to ~/.kugetsu/
PM can NEVER write to repositories/*, skills/*, or any directory outside ~/.kugetsu/
If asked to write outside boundary, PM must delegate via kugetsu start github.com/shoko/kugetsu#<issue> <task>

Fixes #52

PM violated NEVER write code constraint by writing directly to SKILL.md instead of delegating.

## Summary - Added explicit **Write Permissions** section to PM skill defining what PM can and cannot write - PM can ONLY write to `~/.kugetsu/` - PM can NEVER write to `repositories/*`, `skills/*`, or any directory outside `~/.kugetsu/` - If asked to write outside boundary, PM must delegate via `kugetsu start github.com/shoko/kugetsu#<issue> <task>` ## Fixes #52 PM violated NEVER write code constraint by writing directly to SKILL.md instead of delegating.

shoko added 1 commit 2026-04-01 00:00:45 +02:00

fix(pm): add explicit write permissions boundary to prevent repo file writes 449dfaecc6

Issue #52: PM violated NEVER write code constraint by writing directly to
repo files (SKILL.md) instead of delegating to a dev agent.

Added explicit Write Permissions section defining:
- PM can ONLY write to ~/.kugetsu/
- PM can NEVER write to repositories/*, skills/*, or any dir outside ~/.kugetsu/
- If asked to write outside ~/.kugetsu/, must delegate via kugetsu start

shoko referenced this pull request

2026-04-01 00:00:58 +02:00

Bug: PM violated NEVER write code constraint - wrote queue scripts directly instead of delegating #52

han commented

2026-04-01 00:07:22 +02:00

First-time contributor

I think PM can ONLY write to:

~/.kugetsu/queue.json - Queue state
~/.kugetsu/logs/* - Your logs

the rest, PM can read but not write. what do you think?

also for point 27 when delegating to a dev agent, it should be:

kugetsu start //#

normally it can be pulled from git remote and git config. for issue and task description, PM should fill it.

also, PM Agent should not write new kugetsu script even if its internal use only. delegate to dev to create it as a new feature by creating a new issue and new PR like the normal development, but then pm agent can test if its working as needed or not.

I think PM can ONLY write to: - `~/.kugetsu/queue.json` - Queue state - `~/.kugetsu/logs/*` - Your logs the rest, PM can read but not write. what do you think? also for point 27 when delegating to a dev agent, it should be: kugetsu start <git server domain>/<git username>/<git repo url>#<issue> <task description> normally it can be pulled from git remote and git config. for issue and task description, PM should fill it. also, PM Agent should not write new kugetsu script even if its internal use only. delegate to dev to create it as a new feature by creating a new issue and new PR like the normal development, but then pm agent can test if its working as needed or not.

shoko referenced this issue from a commit

2026-04-01 00:14:01 +02:00

address PR #55 review: tighten write permissions to queue.json and logs/* only

shoko added 1 commit 2026-04-01 00:14:01 +02:00

address PR #55 review: tighten write permissions to queue.json and logs/* only cb0ada9e1c

- PM can ONLY write to ~/.kugetsu/queue.json and ~/.kugetsu/logs/* (was entire ~/.kugetsu/)
- Update delegation format to git.fbrns.co/shoko/kugetsu#<issue>
- PM must not write new kugetsu scripts - delegate via issue/PR workflow
- Update examples and violation cases to reflect stricter boundaries

han commented

2026-04-01 00:18:21 +02:00

First-time contributor

git.fbrns.co/shoko/kugetsu#

it keeps saying git.fbrns.co/shoko/kugetsu#, we want these to be dynamic. in a way that, git server domain can change. it can be gitlab.com, github.com, anything, should be agnostic. the same thing with user and repository urls. we are not using kugetsu for this specific repository only. can we somehow patch this?

> git.fbrns.co/shoko/kugetsu#<issue> it keeps saying git.fbrns.co/shoko/kugetsu#<issue>, we want these to be dynamic. in a way that, git server domain can change. it can be gitlab.com, github.com, anything, should be agnostic. the same thing with user and repository urls. we are not using kugetsu for this specific repository only. can we somehow patch this?

shoko added 1 commit 2026-04-01 00:20:22 +02:00

make delegation format agnostic to git server 71cab655fc

Replace hardcoded git.fbrns.co/shoko/kugetsu with dynamic
<domain>/<user>/<repo> format pulled from git remote and config.
Makes PM skill usable with github.com, gitlab.com, or any git server.

han approved these changes 2026-04-01 00:26:48 +02:00

han left a comment

First-time contributor

lgtm

shoko referenced this pull request

2026-04-01 00:45:47 +02:00

PM Agent: opencode external_directory permission fails for subdirectory paths #36

shoko merged commit 6c23d4f5e9 into main

2026-04-01 08:09:31 +02:00

shoko referenced this issue from a commit

2026-04-01 08:09:33 +02:00

Merge pull request 'fix(pm): add explicit write permissions boundary (fixes #52)' (#55) from fix/issue-52-pm-write-boundaries into main