القائمة
Create or update a project BRIEF.md — scaffolds planning structure for work that crosses the 5-file / multi-session threshold
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Review all pending changes against repo conventions before committing
Mark files as human-reviewed with specific validation types
Harvest and locally merge changes from a paude container session. Use when pulling agent work from paude, running paude harvest, merging session commits, importing submodule changes from a container, or fixing failed harvest/submodule fetch.
Start a paude container session for fire-and-forget agent work. Use when creating a paude session, delegating a task to paude, running work in an isolated container, setting up a paude worktree, or launching pi/claude/gemini in podman.
Write a task spec file for a paude container agent. Use when delegating work to paude, preparing a paude prompt-file, writing fire-and-forget agent tasks, or scoping submodule work for harvest.
Diagnose a running or stalled paude container session. Use when paude seems stuck, harvest returned empty, checking paude status, debugging 403 proxy blocks, or deciding wait vs harvest vs reset.
| name | brief |
| description | Create or update a project BRIEF.md — scaffolds planning structure for work that crosses the 5-file / multi-session threshold |
| argument-hint | [project-name] |
| allowed-tools | Read Write Shell Glob |
/start flags a brief gap for active workIf $ARGUMENTS is provided, use it as the project name (slug format: kebab-case).
If not provided:
gpu-vgpu-gitops work — use that name, or suggest one?"ls .planning/<project-name>/ 2>/dev/null
If a BRIEF already exists, read it and ask: "A brief already exists — update it or start fresh?"
Before writing, collect:
git log --oneline -10 -- <relevant paths>Do not ask the user for information you can derive from the repo.
Create .planning/<project-name>/BRIEF.md:
# <Project Name>
> **Status:** In Progress
> **Started:** <date>
> **Owner:** <from ABOUT.md if available>
## Audience and Purpose
**Reader:** [Who reads this brief — role or person]
**Enables:** [What decision or scope boundary this anchors]
## Problem Statement
[One paragraph — what problem is this work solving and why now?]
## Scope
[What's in. Be specific about boundaries.]
**Out of scope:** [What's explicitly excluded — prevents scope creep]
## Success Criteria
- [ ] [Concrete, checkable outcome]
- [ ] [Concrete, checkable outcome]
## Constraints
- [Hard constraints: hardware, versions, patterns already established]
## Key Decisions
| Decision | Choice | Rationale |
|----------|--------|-----------|
| [topic] | [what was decided] | [why] |
## Related
- [Links to key files, runbooks, research]
Create .planning/<project-name>/whats-next.md with a stub:
# Checkpoint — <date>
**In progress:** [current task]
**Just completed:** [what landed before this brief was created — from git log]
**Next step:** [immediate next action]
**Git:** `<HEAD commit hash and message>`
git add .planning/<project-name>/
git commit -m "chore(planning): create <project-name> project brief"
If this skill was invoked because a brief gap was detected (not by explicit user request), after creating the brief say:
"Brief created at
.planning/<project-name>/BRIEF.md. I'll use this as the scope anchor going forward — handoffs will reference it rather than carrying all context themselves."