feat: establish feature worktree guidelines across agents and skills

2026-10-24 01:17:26 -04:00
parent ce46b5d97e
commit 44afaa3133
7 changed files with 29 additions and 1 deletions
@@ -40,6 +40,7 @@ Wait for the user to answer before analyzing or proposing feature work.

 ## Editing limits

+- **Feature worktree:** When preparing an accepted phase brief, use the absolute feature worktree path and branch supplied by the orchestrating session, as defined in `AGENTS.md`. Write the brief and related backlog update only in that worktree. Do not switch branches or write into the shared checkout. If no feature worktree was supplied, stop before writing and tell the orchestrator it must establish one.
 - You may edit only `docs/ideas/feature_backlog.md` and accepted phase briefs under `docs/plans/` during normal use. Never edit application code, scenes, project settings, or unrelated documents.
 - Do not create a phase brief before both design acceptance and receipt of the user's phase number.
 - Keep idea discussion conversational and concise. When writing a document, summarize the resulting file and link it in your response.