adk-core:temp-folder

Source

plugins/adk-core/skills/temp-folder/SKILL.md

Skill Body

temp-folder — canonical .temp/ layout authority

The single source of truth for .temp/task-<slug>/ directory layout. Other skills shell out to bin/adk-task-slug to create their workspace.

When to use

• A skill is starting and needs a fresh workspace.
• The user asks “where does adk put its working files?”.
• Documentation links want to reference the layout.

When NOT to use

• Final / committed artifacts → put them in the repo, not .temp/.
• Cleaning .temp/ → that’s the operator’s manual job. The folder is durable session context.

Common prompts

• “create a workspace for this task”
• “where do .temp/ files go?”
• “show me the .temp/ layout”

Inputs

Layout

1.temp/task-<slug>/2├── prompt.txt                          # verbatim user prompt (auto / outer skill writes this)3├── skill-plan.md                       # auto / prompt-expand output4├── context.md                          # context-gather output5├── scope.md                            # if scoping ran6├── design.md                           # if design ran (rare for adk)7├── plan.md                             # implementer plan (code-* skills)8├── review/9│   ├── findings.md10│   ├── postback.md11│   └── reconciliation.md12├── investigation/13│   ├── datadog.md14│   ├── mixpanel.md15│   ├── statsig.md16│   ├── snowflake.md17│   ├── deploy.md18│   ├── incident.md19│   └── rca.md20├── docs/21│   ├── draft.md22│   └── review.md23├── validation/24│   ├── auto-validator.md25│   └── per-skill/<skill>.md26└── report.md                           # final consolidated report

Top-level (non-task) areas

Workflow

1Phase 1 — preflight2  - Verify `bin/adk-task-slug` exists and is executable.3  - Verify the target scope is writable unless --print-only is set.4  - No MCP or connector is required.56Phase 2 — create or print7  - Receive slug (or prompt to slug-ify).8  - Run bin/adk-task-slug "<input>" [--print] [--date] [--scope].9  - The script emits the slug and creates .temp/task-<slug>/ in cwd.10  - Return the slug + the absolute path to the workspace.

Persona

Convention enforcer. The .temp/ layout is the contract; you keep it consistent across skills.

See references/persona.md.

Constitution

Must do:

1. Slugs are kebab-case, max 6 words, derived from prompt nouns/verbs.
2. Every skill writes ALL artifacts under .temp/task-<slug>/. No exceptions.
3. The skill creating a new task is responsible for the slug.
4. .temp/ is gitignored. Verify before any write.
5. Slug is preserved across skill invocations within a session (the dispatcher passes it down).

Must not do:

1. Auto-clean old .temp/task-*/ folders.
2. Use a date-only slug when descriptive nouns are available.
3. Write outside .temp/task-<slug>/ from a skill that’s mid-task.
4. Allow whitespace, uppercase, or punctuation in slugs.

Anti-patterns

See references/anti-patterns.md. Highlights:

• “I’ll just write to the repo root for now” — no. .temp/ exists for this.
• Auto-deleting old task folders. Old artifacts are research material; the user prunes manually.
• Using a different slug per skill in the same session. One slug per task.

Output

The skill emits two things to stdout:

1slug: <slug>2path: <absolute-path-to-.temp/task-<slug>/>

References shipped with this skill