[chore] Organize work-tmp with per-feature subdirectories for agent output#14157
Draft
sfc-gh-lwilby wants to merge 1 commit intodevelopfrom
Draft
[chore] Organize work-tmp with per-feature subdirectories for agent output#14157sfc-gh-lwilby wants to merge 1 commit intodevelopfrom
sfc-gh-lwilby wants to merge 1 commit intodevelopfrom
Conversation
Made-with: Cursor Co-authored-by: lawilby <laura.wilby+oss@snowflake.com>
Contributor
✅ PR preview is ready!
|
Contributor
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Contributor
There was a problem hiding this comment.
Pull request overview
Introduces a clearer convention for organizing ephemeral development artifacts under work-tmp/, separating per-feature working materials from general throwaway files and Claude plan outputs.
Changes:
- Document a
work-tmp/features/<feature-name>/structure for per-feature implementation plans, notes, and test apps. - Keep
work-tmp/available for one-off temporary files. - Update Claude Code configuration to write plans to
work-tmp/plans/.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| AGENTS.md | Adds the new work-tmp/features/<feature-name>/ convention and recommended internal structure. |
| .github/copilot-instructions.md | Mirrors the updated work-tmp/ organization guidance for Copilot usage. |
| .cursor/rules/overview.mdc | Mirrors the updated work-tmp/ organization guidance for Cursor rules. |
| .claude/settings.json | Moves plansDirectory to ./work-tmp/plans to separate plan outputs from feature working files. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Describe your changes
Introduces a
work-tmp/features/<feature-name>/convention for organizing per-feature working files instead of dumping everything flat intowork-tmp/.Right now
work-tmp/is a flat bucket mixing debug logs, implementation plans, test scripts, and throwaway scratch files. This gives feature work its own organized space with a suggested internal structure.work-tmp/features/<feature-name>/withimplementation-plan.md,notes.md,test-apps/plansDirectorymoved towork-tmp/plans/to separate auto-generated session plans from feature working fileswork-tmp/Working files accumulated during feature development often have a longer lifespan than truly temporary files — they're useful as context while the feature is in progress and could feed into implementation plans, tech specs, or other longer-lived documentation. This is a first step toward giving
work-tmp/more structure; further organization (e.g. separating scratch files from feature work) could follow.Screenshot or video (only for visual changes)
N/A
GitHub Issue Link (if applicable)
N/A
Testing Plan
Contribution License Agreement
By submitting this pull request you agree that all contributions to this project are made under the Apache 2.0 license.