Skills akievo
Persistent project planning for AI agents. Create, manage, and track long-term goals using structured Kanban boards that survive session resets.
install
source · Clone the upstream repo
git clone https://github.com/openclaw/skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/akievo/akievo" ~/.claude/skills/openclaw-skills-akievo && rm -rf "$T"
OpenClaw · Install into ~/.openclaw/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.openclaw/skills && cp -r "$T/skills/akievo/akievo" ~/.openclaw/skills/openclaw-skills-akievo && rm -rf "$T"
manifest:
skills/akievo/akievo/SKILL.mdsource content
Akievo — Agent Plan Mode
You have access to Akievo, a structured project management system. Use it as your persistent memory and planning layer for long-term goals. Akievo boards survive session resets — they are your source of truth.
Core Principles
- Always check before creating. At the start of every session, call
to find existing plans before creating new ones.list_boards - One board per goal. Each major goal or project gets its own board. Prefix agent-created boards with
(e.g.,[Agent]
).[Agent] Launch SaaS Product - Lists are phases. Use lists to represent sequential phases or categories (e.g., "Research", "Build", "Launch", "Done").
- Cards are tasks. Each actionable step is a card. Include clear titles and descriptions.
- Respect human edits. The human may add, remove, reprioritize, or comment on cards. Always re-read the board before acting. Never undo or override human changes.
Session Start Pattern
Every time a new session begins:
- Call
to find boards prefixed withlist_boards[Agent] - If a relevant board exists, call
with its ID to load the full stateget_board - Read the board's
field for context (goal, timeline, assumptions)project_memory - Identify the next unblocked, incomplete task
- Report status to the user: what's done, what's next, any blockers
Creating a New Plan
When the user describes a new goal:
- Call
to find available workspaceslist_workspaces - Use
to scaffold the entire plan in one call:create_board_with_tasks- Break the goal into 3–6 phases (lists)
- Each phase gets 3–8 concrete tasks (cards)
- Add checklists for tasks with sub-steps
- Set priorities:
,critical
,high
,mediumlow - Set due dates when the user provides a timeline
- Create dependencies between tasks that have a natural order using
bulk_create_dependencies - Present the plan to the user and ask for feedback before proceeding
Working on Tasks
When executing on a plan:
- Pick the next unblocked, highest-priority incomplete card
- Work on it (using your other tools — coding, research, writing, etc.)
- Add progress updates as comments using
add_comment - When done, call
to mark it finishedcomplete_card - If blocked, call
with a clear reasonblock_card - Move to the next task
Updating the Plan
As work progresses, the plan may need adjustment:
- Add new tasks:
in the appropriate listcreate_card - Update details:
to change title, description, priority, or due dateupdate_card - Reorder:
to shift tasks between phasesmove_card - Add sub-tasks:
for granular stepsadd_checklist_item - Never delete cards without asking the user first
Progress Reporting
When the user asks for a status update:
- Call
to get current stateget_board - Count completed vs total cards per list
- Highlight blocked items and their reasons
- Identify upcoming due dates
- Suggest next actions
Important Safety Rules
- Never delete a board without explicit user confirmation
- Never archive cards without asking
- Always re-read the board before making changes (the human may have edited it)
- Log your work — add comments to cards explaining what you did and why
- Stay scoped — only modify boards you created or were explicitly asked to manage