القائمة
Activate when creating any summary, report, or output file. Ensures files go to correct directories (summaries/, memory/, stories/, bugs/). Mirrors what summary-file-enforcement hook enforces.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Activate when a subagent completes work and needs continuation check. Activate when a task finishes to determine next steps or when detecting work patterns in user messages. Governs automatic work continuation and queue management.
Activate when user asks to commit, push changes, create a PR, open a pull request, or submit changes for review. Activate when process skill reaches commit or PR phase. Provides commit message formatting and PR structure. PRs default to dev branch, not main. Works with git-privacy skill.
Orchestrate the end-to-end development workflow with autonomous quality gates. Use when users ask to implement/run workflow phases, start or continue development, handle review/QA findings, or process actionable comments by routing through create-work-items -> plan-work-items -> run-work-items. Enforces TDD by default for implementation work and only pauses for genuine decisions.
Activate when user asks to release, bump version, cut a release, merge to main, or tag a version. Handles version bumping (semver), CHANGELOG updates, PR merging, git tagging, and GitHub release creation.
Create and classify typed work items (epic, story, feature, bug, finding, work-item) in the configured tracking backend. Use when users ask to create/capture work or when actionable findings/comments are discovered from review, PR feedback, QA, regressions, or defect reports.
Plan and prioritize existing typed work items with dependency and hierarchy validation. Use when users ask to sequence work, when new actionable findings/comments were captured, or when blockers/dependencies changed before execution.
| name | file-placement |
| description | Activate when creating any summary, report, or output file. Ensures files go to correct directories (summaries/, memory/, stories/, bugs/). Mirrors what summary-file-enforcement hook enforces. |
| category | enforcement |
| scope | development |
| subcategory | safeguards |
| tags | ["development","enforcement","file","placement"] |
| version | 10.2.14 |
| author | Karsten Samaschke |
| contact-email | karsten@vanillacore.net |
| website | https://vanillacore.net |
Apply correct file placement rules for all output files.
File placement is enforced by hooks - violations will be blocked. This skill ensures you understand the rules so your work isn't rejected.
| File Type | Required Directory | Examples |
|---|---|---|
| Summaries | summaries/ | execution-summary.md, review-summary.md |
| Reports | summaries/ | analysis-report.md, audit-report.md |
| Stories | stories/ | STORY-001-feature.md |
| Bugs | bugs/ | BUG-001-issue.md |
| Memory (exports) | memory/exports/ | memory/exports/patterns/oauth2.md |
| Documentation | docs/ | api-docs.md, architecture.md |
NEVER place these in the wrong location:
docs/ or project rootdocs/ or project rootmemory/exports/Only these filenames may be ALL-CAPS:
All other files: Use lowercase-kebab-case
execution-summary.md (correct)EXECUTION-SUMMARY.md (blocked)The summary-file-enforcement.js hook will:
summaries/Ask yourself:
summaries/memory/exports/<category>/ (category: architecture, implementation, issues, patterns)This skill provides guidance - you understand the rules. The hook provides enforcement - violations are blocked.
Together they ensure consistent file organization even when: