From 9785b28496c6cdc7d753bf7aeaab0659de0f51b2 Mon Sep 17 00:00:00 2001 From: Dave Date: Thu, 26 Feb 2026 19:33:26 +0000 Subject: [PATCH] story-kit: create 222_story_scaffolded_agent_permissions_should_be_tech_stack_agnostic --- ...rmissions_should_be_tech_stack_agnostic.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 .story_kit/work/1_upcoming/222_story_scaffolded_agent_permissions_should_be_tech_stack_agnostic.md diff --git a/.story_kit/work/1_upcoming/222_story_scaffolded_agent_permissions_should_be_tech_stack_agnostic.md b/.story_kit/work/1_upcoming/222_story_scaffolded_agent_permissions_should_be_tech_stack_agnostic.md new file mode 100644 index 0000000..8e3f831 --- /dev/null +++ b/.story_kit/work/1_upcoming/222_story_scaffolded_agent_permissions_should_be_tech_stack_agnostic.md @@ -0,0 +1,19 @@ +--- +name: "Scaffolded agent permissions should be tech-stack agnostic" +--- + +# Story 222: Scaffolded agent permissions should be tech-stack agnostic + +## User Story + +As a developer using Story Kit with a non-Rust/non-Node project, I want the scaffolded .claude/settings.json permissions to only include generic commands (git, ls, etc.), so that the allowlist isn't cluttered with irrelevant cargo/pnpm rules. + +## Acceptance Criteria + +- [ ] Scaffolded .claude/settings.json only includes generic tool-agnostic commands (git, ls, mkdir, etc.) +- [ ] Onboarding agent adds project-specific permission entries (cargo, pnpm, go, etc.) based on the tech stack chosen during setup +- [ ] Existing projects are not broken by the change (additive permissions still work) + +## Out of Scope + +- TBD