Remake skillu project
This commit is contained in:
@@ -1,88 +1,128 @@
|
||||
---
|
||||
name: project
|
||||
aliases: [proj]
|
||||
description: >
|
||||
Project management — long-running things with notes, next-steps, and status.
|
||||
Use when user mentions "project".
|
||||
Switch between named ongoing projects, each with its own persistent
|
||||
context, carried forward across turns until the user switches or ends it.
|
||||
Triggers on: "project X", "switch to project X", "we're working on X",
|
||||
"end project" / "no project". For a long-lived, named work context — not a
|
||||
single task to plan and execute, and not a short or global fact to
|
||||
remember.
|
||||
---
|
||||
|
||||
# Project
|
||||
|
||||
File-backed project store in `projects/`. Each project is one markdown file
|
||||
with YAML frontmatter (`status`, `priority`, `created`, `slug`) and a free-form
|
||||
body for notes and next-steps.
|
||||
Named, long-lived work contexts. Each project keeps its own instructions, its
|
||||
own history, its own current-state summary, and its own generated files —
|
||||
separate from every other project and from the agent's general memory.
|
||||
|
||||
## Backend
|
||||
## Layout
|
||||
|
||||
`skills/project/scripts/project.py` — deterministic CRUD for frontmatter and
|
||||
basic operations. Agent handles all body edits via `edit_file` / `apply_patch`.
|
||||
`workspace/projects/<slug>/`:
|
||||
|
||||
## Commands
|
||||
- `prompt.md` — project-specific context/instructions, read in full whenever
|
||||
the project becomes active
|
||||
- `memory.md` — append-only chronological log of decisions and history
|
||||
- `state.md` — living document: the current state/synthesis of the project,
|
||||
edited in place, not appended to
|
||||
- `artifacts/` — generated files (documents, code, data exports, reports)
|
||||
|
||||
### `project add <název>` — create
|
||||
**Which project is active is tracked purely through conversation memory —
|
||||
nothing is persisted to disk for that.** Once a project is chosen, keep
|
||||
treating it as active for the rest of this conversation; don't re-read its
|
||||
files on every subsequent turn once they're already in context.
|
||||
|
||||
1. Run: `uv run skills/project/scripts/project.py add "<název>" [--priority high|medium|low]`
|
||||
2. Default priority is `medium`.
|
||||
3. Echo: `Created project '<slug>' (priority: <priority>)`
|
||||
## Activation
|
||||
|
||||
### `project list` — list active
|
||||
Triggered by "project X" / "switch to project X" / "we're working on X":
|
||||
|
||||
1. Run: `uv run skills/project/scripts/project.py list`
|
||||
2. Echo JSON output. Format as:
|
||||
```
|
||||
Active projects:
|
||||
- <slug> (priority: high) — <first line of body / project name>
|
||||
```
|
||||
3. If empty → "No active projects."
|
||||
1. Turn `X` into a kebab-case directory name (like picking a slug for a plan
|
||||
file — no need to spell out an algorithm, just pick something sensible).
|
||||
2. **`workspace/projects/<slug>/` already exists** → read `prompt.md`,
|
||||
`memory.md`, and `state.md` in full, then briefly confirm what's active
|
||||
and, if `prompt.md` or `state.md` has content, what context you loaded.
|
||||
3. **It doesn't exist, but the name is a close match to one or more existing
|
||||
projects** (case-insensitive) → ask which one was meant. Don't guess, and
|
||||
don't create a near-duplicate of an existing project.
|
||||
4. **It doesn't exist and there's no close match** → this skill only works
|
||||
with projects that already exist without asking. Ask the user whether to
|
||||
start a new project with that name. Only on explicit yes, create
|
||||
`prompt.md`, `memory.md`, `state.md` (all empty) and `artifacts/`. Never
|
||||
create a project just because a trigger phrase was said.
|
||||
|
||||
### `project show <slug>` — display
|
||||
**Already active:** if the same project is already active in this
|
||||
conversation, don't re-create or re-read anything — just continue.
|
||||
|
||||
1. Run: `uv run skills/project/scripts/project.py show <slug>`
|
||||
2. Echo the full markdown file.
|
||||
## Staying active
|
||||
|
||||
### `project status <slug> <active|paused|done>` — change status
|
||||
Once a project is active, keep applying its `prompt.md` instructions and
|
||||
`state.md` context for the rest of the conversation, until the user switches
|
||||
or ends it.
|
||||
|
||||
1. Run: `uv run skills/project/scripts/project.py status <slug> <status>`
|
||||
2. Echo: `Project '<slug>' is now <status>.`
|
||||
If a long gap or an ambiguous reference makes it unclear whether the project
|
||||
is still the right context (e.g. the conversation has clearly moved to an
|
||||
unrelated topic), ask rather than silently carrying it forward or silently
|
||||
dropping it.
|
||||
|
||||
### `project next <slug> <text>` — set next step
|
||||
## Switching and ending
|
||||
|
||||
1. Read the project file.
|
||||
2. Use `edit_file` to replace the content under `## Další krok` with the new text.
|
||||
3. If the section does not exist, add it before the end of the file.
|
||||
4. Echo: `Next step for '<slug>' updated.`
|
||||
- **"switch to Y"** → run the Activation flow for Y; Y becomes active
|
||||
instead.
|
||||
- **"end project" / "no project" / "stop working on X"** → stop treating any
|
||||
project as active. Say so. Don't delete anything.
|
||||
- With no active project, behave normally — never force a project onto an
|
||||
unrelated request.
|
||||
|
||||
### `project note <slug> <text>` — add a note
|
||||
## Writing to memory.md
|
||||
|
||||
1. Read the project file.
|
||||
2. Use `edit_file` to append a bullet under `## Poznámky`:
|
||||
`- <today>: <text>`
|
||||
3. If `## Poznámky` does not exist, add it after the first heading.
|
||||
4. Echo: `Note added to '<slug>'.`
|
||||
Append only — never rewrite or reorder existing entries. One entry per
|
||||
decision, dead end, or noteworthy piece of history:
|
||||
|
||||
### `project switch <slug>` — session context
|
||||
```
|
||||
- YYYY-MM-DD: <terse entry, reformulated, not verbatim>
|
||||
```
|
||||
|
||||
1. Run `my(action="set", key="project_context", value="<slug>")`.
|
||||
2. Echo: `Switched to project '<slug>'. Next project commands without slug will use this context.`
|
||||
3. If a command is missing a slug and `project_context` is set, use it automatically.
|
||||
Write an entry when a decision is made, a dead end is found, or a fact
|
||||
central to the project's ongoing context emerges — not for routine
|
||||
back-and-forth. When in doubt whether something is memory-worthy, prefer not
|
||||
writing it; `memory.md` is for what a future conversation needs to pick up
|
||||
the thread, not a transcript.
|
||||
|
||||
## Rules
|
||||
## Maintaining state.md
|
||||
|
||||
- **Slug** = kebab-case from first 4 words of the name. Used as filename (`<slug>.md`).
|
||||
- **Frontmatter** is read-only for the agent — never edit it directly in the file.
|
||||
Use `project.py status` to change status.
|
||||
- **Body edits** (notes, next-step, structure changes) are always done by the agent
|
||||
via `edit_file` / `apply_patch`.
|
||||
- **No database** — pure markdown files. Git-friendly, one commit per change.
|
||||
- **Session context** (`project switch`) lives only in `my` scratchpad and is lost
|
||||
on restart. Re-run `project switch` after restart if needed.
|
||||
- **Priority** = `high` | `medium` | `low`. `list` sorts by priority (high first).
|
||||
- **Status** = `active` | `paused` | `done`. `list` shows only `active`.
|
||||
Unlike `memory.md`, `state.md` is edited in place: surgically update the
|
||||
relevant section when the project's current state or understanding has
|
||||
moved on enough that the old text would mislead a reader. It answers "where
|
||||
is this now", not "what happened" — old content gets replaced, not appended
|
||||
to. If it's still empty and the project has accumulated enough context to
|
||||
synthesize, offer to draft it.
|
||||
|
||||
## Artifacts
|
||||
|
||||
Files generated while working on the project (documents, code, data exports,
|
||||
reports) go in `workspace/projects/<slug>/artifacts/` instead of scattered
|
||||
elsewhere. Name them descriptively; no numbering or index file needed at
|
||||
this scale.
|
||||
|
||||
## Listing
|
||||
|
||||
**"list projects" / "which projects exist":** list the directory names under
|
||||
`workspace/projects/`. If none exist, say so.
|
||||
|
||||
## Edge cases
|
||||
|
||||
- `project add` with existing slug → error, do not overwrite.
|
||||
- `project show` / `project status` / `project next` / `project note` with
|
||||
missing slug → "Project '<slug>' not found."
|
||||
- Missing `## Poznámky` or `## Další krok` → agent creates the section.
|
||||
- Empty `projects/` → `list` returns empty array.
|
||||
- "project" with no name → ask which project.
|
||||
- The project directory exists but one or more of `prompt.md` / `memory.md`
|
||||
/ `state.md` is missing (e.g. created by hand) → create the missing
|
||||
file(s) empty, don't error.
|
||||
- Deleting or renaming a project is out of scope for this skill — point the
|
||||
user at `workspace/projects/<slug>/` to do it by hand.
|
||||
|
||||
## Rules
|
||||
|
||||
- This skill's body is English; reply to the user in their own language.
|
||||
- Never fabricate project content — `prompt.md`, `memory.md`, and `state.md`
|
||||
only grow from what the user actually said or what actually happened.
|
||||
- Never create a new project without the user's explicit confirmation.
|
||||
- Don't force a project context onto an unrelated request.
|
||||
- The Dream memory processor must not touch `workspace/projects/` — it is
|
||||
outside the memory and skills Dream curates.
|
||||
|
||||
Reference in New Issue
Block a user