basic_task_memo
Sync and update your project planning and progress documentation.
Install
mkdir -p .claude/skills/basic-task-memo && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12663" && unzip -o skill.zip -d .claude/skills/basic-task-memo && rm skill.zipInstalls to .claude/skills/basic-task-memo
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when creating or updating docs/plan.md, docs/tasks.md, or docs/progress.md, or when asked about plan/todo/progress and next steps.Key capabilities
- →Read docs/plan.md, docs/tasks.md, and docs/progress.md
- →Update docs/plan.md for scope or strategy changes
- →Update docs/tasks.md for actionable work items
- →Update docs/progress.md for completed work
- →Keep planning, TODOs, and progress logs consistent
How it works
The skill reads existing planning documents, then updates them based on user input, ensuring consistency across strategic plans, actionable tasks, and progress logs.
Inputs & outputs
When to use basic_task_memo
- →Updating project TODOs
- →Recording a completed task in progress.md
- →Refining the project plan
- →Syncing tasks with current progress
About this skill
Basic Task Memo
Goal
Keep planning, TODOs, and progress logs consistent and actionable without mixing concerns.
Workflow
- Read memos
- Open
docs/plan.md,docs/tasks.md, anddocs/progress.md. - Summarize the current goals and next actions; do not invent tasks.
- Update plan (
docs/plan.md) when scope or strategy changes
- Keep goals and success criteria measurable and short.
- Record decisions, risks, and open questions.
- Avoid task-level detail here; keep it strategic.
- Update tasks (
docs/tasks.md) for actionable work
- Use small, checkable items with clear outcomes.
- Keep each item independently completable.
- Remove or check off completed tasks.
- Update progress (
docs/progress.md) for completed work
- Append completed, high-signal changes as bullet points.
- Keep entries factual and brief.
- Do not add future work here.
- Keep files in sync
- When a task completes, mark it in
docs/tasks.mdand add a progress entry. - When a plan changes, align tasks to match it.
Optional Template (use only if a file is missing)
# Implementation Plan: <short title>
1. Goals and Targets
- Do:
- Target:
1. Success Criteria
-
1. Current State
-
1. Scope
-
1. Approach
-
1. Risks / Open Questions
-
Guardrails
- Keep updates short and free of secrets or tokens.
- Preserve the existing structure when it is already in use.
- Confirm updates in the response and reference the file paths.
When not to use it
- →When the user is not creating or updating planning documents
- →When the user is not asking about plan, todo, progress, or next steps
Limitations
- →Keep updates short and free of secrets or tokens
- →Preserve the existing structure when it is already in use
- →Avoid task-level detail in docs/plan.md
How it compares
This skill enforces a structured approach to project documentation, separating strategic plans, detailed tasks, and progress updates into distinct files, which is more organized than a single, undifferentiated log.
Compared to similar skills
basic_task_memo side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| basic_task_memo (this skill) | 0 | 7mo | No flags | Beginner |
| session-handoff | 13 | 2mo | Review | Beginner |
| spec-to-backlog | 8 | 4mo | No flags | Intermediate |
| create-handoff | 3 | 6mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by Silviase
View all by Silviase →You might also like
session-handoff
davila7
Creates comprehensive handoff documents for seamless AI agent session transfers. Triggered when: (1) user requests handoff/memory/context save, (2) context window approaches capacity, (3) major task milestone completed, (4) work session ending, (5) user says 'save state', 'create handoff', 'I need to pause', 'context is getting full', (6) resuming work with 'load handoff', 'resume from', 'continue where we left off'. Proactively suggests handoffs after substantial work (multiple file edits, complex debugging, architecture decisions). Solves long-running agent context exhaustion by enabling fresh agents to continue with zero ambiguity.
spec-to-backlog
atlassian
Automatically convert Confluence specification documents into structured Jira backlogs with Epics and implementation tickets. When Claude needs to: (1) Create Jira tickets from a Confluence page, (2) Generate a backlog from a specification, (3) Break down a spec into implementation tasks, or (4) Convert requirements into Jira issues. Handles reading Confluence pages, analyzing specifications, creating Epics with proper structure, and generating detailed implementation tickets linked to the Epic.
create-handoff
parcadei
Create handoff document for transferring work to another session
moai-workflow-project
modu-ai
Integrated project management system with documentation, language initialization, and template optimization modules. Use when setting up projects, generating documentation, configuring multilingual support, or optimizing templates.
granola-core-workflow-b
jeremylongshore
Post-meeting note processing and sharing workflow with Granola. Use when reviewing meeting notes, sharing with team members, or processing action items after meetings. Trigger with phrases like "granola post meeting", "share granola notes", "granola follow up", "process meeting notes", "granola action items".
reporting
comeredon
Final pipeline execution report format. Defines the structure, agent registry, Mermaid gantt chart, and change summary. Used by AnalystAgent in Phase 6.