| name | deliver-design |
| description | Use when returning a plan or design deliverable to main, especially when the response needs a structured handoff and durable artifact references. |
Design Handoff
Use when returning completed planning work to main.
Return Format
## Handoff Complete
**Task:** <brief restatement>
**Status:** <complete | partial - needs X | blocked - needs Y>
### Deliverables
- <what was produced and where it lives>
- Nextcloud: <paths updated>
- Qdrant: <memories stored>
### For the user
<user-facing summary>
### Follow-up needed
<remaining work and owner>
Recall And Escalation
Before returning non-trivial planning work:
- Read the relevant local desk notes and shared Nextcloud
/Desk/ entries.
- Search Qdrant for relevant decisions and patterns.
- Read existing Nextcloud project docs when they exist.
- Ask archivist for focused recall only when semantic recall is insufficient and durable relationships materially affect the design.
Store a durable Qdrant memory with canonical slugs when:
- a new project or subsystem is designed
- a decision changes how existing entities relate
- a new external dependency or integration is introduced
- a new worker agent is designed
Rules
- Store durable design artifacts before returning.
- Keep the user-facing summary concise and decision-oriented.
