\r \r

Daily Workflow Skill (English Version)\r

\r Manage daily work sessions with automated project documentation tracking and AI-to-AI handover support.\r \r

When to Use This Skill\r

\r Trigger this skill when the user mentions:\r

• "starting work" / "start of day" / "let's begin" - Starting the work day\r
• "ending work" / "end of day" / "wrapping up" - Ending the work day\r \r These phrases indicate intentional work session boundaries where project state should be captured and restored.\r \r

Core Workflow\r

\r

Phase 1: Start Work Session\r

\r Execute the following sequence when the user indicates work is starting:\r \r

1. Ensure Docs Directory Exists\r
   • Check if Docs/ directory exists in workspace root\r
   • Create Docs/ if it does not exist\r \r
2. Check and Create Required Files\r
   • Verify these five files exist in Docs/:\r
     • PROJECT_TARGET.md - Project objectives and goals\r
     • PROJECT_STATUS.md - Current project status\r
     • COMPLETED_JOBS.md - Completed work items\r
     • PENDING_JOBS.md - Pending/incomplete work items\r
     • NEXT_STEPS.md - Planned next steps\r
   • Create any missing files with appropriate template headers\r \r
3. Read All Documentation\r
   • Read all five files from Docs/\r
   • Extract key information:\r
     • Current project objectives\r
     • Latest project status\r
     • Recently completed work\r
     • Pending tasks and blockers\r
     • Planned next steps\r \r
4. Present Work Session Briefing\r
   • Summarize current project state\r
   • Highlight completed work since last session\r
   • Identify pending tasks\r
   • Suggest priority work for current session\r
   • Ask user for confirmation or adjustments to the plan\r \r

Phase 2: End Work Session\r

\r Execute the following sequence when the user indicates work is ending:\r \r

1. Update Completed Jobs\r
   • Append today's completed work items to Docs/COMPLETED_JOBS.md\r
   • Use format: `## [YYYY-MM-DD]\

• [completed item 1]\
• [completed item 2]`\r
  • Include sufficient detail for another AI to understand what was done\r \r

2. Update Pending Jobs\r
   • Update Docs/PENDING_JOBS.md with:\r
     • Tasks started but not completed\r
     • Blockers encountered\r
     • Tasks deferred to next session\r
   • Remove completed items from pending list\r \r
3. Update Project Status\r
   • Update Docs/PROJECT_STATUS.md with:\r
     • Current completion percentage\r
     • Key milestones reached\r
     • Current focus area\r
     • Any changes in project direction\r \r
4. Update Project Target (if needed)\r
   • Modify Docs/PROJECT_TARGET.md only if:\r
     • Project objectives have changed\r
     • New requirements discovered\r
     • Scope adjustments needed\r
   • Otherwise, leave unchanged\r \r
5. Update Next Steps\r
   • Write clear, actionable next steps to Docs/NEXT_STEPS.md\r
   • Include:\r
     • Specific tasks to tackle next session\r
     • Priority order\r
     • Any prerequisites or dependencies\r
     • Context needed to resume work immediately\r \r
6. Present Session Summary\r
   • Summarize what was completed\r
   • List updated documentation files\r
   • Confirm next steps are clearly documented\r
   • Ensure handover-ready state for next AI\r \r

File Templates\r

\r When creating missing files, use these templates:\r \r

PROJECT_TARGET.md\r

# Project Target\r
\r
## Project Overview\r
[Describe the project's main objective]\r
\r
## Key Goals\r
- [Goal 1]\r
- [Goal 2]\r
\r
## Success Criteria\r
- [Criterion 1]\r
- [Criterion 2]\r
\r
## Last Updated\r
[YYYY-MM-DD]\r
```\r
\r
### PROJECT_STATUS.md\r
```markdown\r
# Project Status\r
\r
## Current Status\r
[Brief description of current state]\r
\r
## Completion\r
[XX]% complete\r
\r
## Current Focus\r
[What is being worked on now]\r
\r
## Recent Milestones\r
- [YYYY-MM-DD] [Milestone description]\r
\r
## Last Updated\r
[YYYY-MM-DD]\r
```\r
\r
### COMPLETED_JOBS.md\r
```markdown\r
# Completed Jobs\r
\r
## [YYYY-MM-DD]\r
- [Completed task 1]\r
- [Completed task 2]\r
\r
## [YYYY-MM-DD]\r
- [Completed task 1]\r
```\r
\r
### PENDING_JOBS.md\r
```markdown\r
# Pending Jobs\r
\r
## High Priority\r
- [ ] [Task 1]\r
- [ ] [Task 2]\r
\r
## Medium Priority\r
- [ ] [Task 3]\r
\r
## Low Priority\r
- [ ] [Task 4]\r
\r
## Blockers\r
- [Blocker description if any]\r
```\r
\r
### NEXT_STEPS.md\r
```markdown\r
# Next Steps\r
\r
## Immediate Actions (Next Session)\r
1. [Action 1 - with context]\r
2. [Action 2 - with context]\r
\r
## Upcoming Tasks\r
- [Task 1]\r
- [Task 2]\r
\r
## Notes for Next AI\r
[Important context, decisions made, things to remember]\r
```\r
\r
## AI-to-AI Handover Principles\r
\r
Write all documentation assuming the next reader will be a different AI instance that needs to:\r
- Understand what was being built and why\r
- Resume work without asking basic questions\r
- Continue the same coding style and conventions\r
- Respect decisions already made\r
\r
**Key practices:**\r
- Write in detail, not shorthand\r
- Explain the "why" not just the "what"\r
- Include code snippets or file references when relevant\r
- Note any workarounds, hacks, or technical debt\r
- Record user preferences and decisions\r
\r
## Workflow Diagram\r
\r
```\r
User indicates work starting\r
    ↓\r
Check Docs/ exists → Create if missing\r
    ↓\r
Check 5 files exist → Create missing with templates\r
    ↓\r
Read all 5 files\r
    ↓\r
Present work session briefing\r
    ↓\r
User works with AI assistance\r
    ↓\r
User indicates work ending\r
    ↓\r
Update COMPLETED_JOBS.md\r
    ↓\r
Update PENDING_JOBS.md\r
    ↓\r
Update PROJECT_STATUS.md\r
    ↓\r
Update PROJECT_TARGET.md (if needed)\r
    ↓\r
Update NEXT_STEPS.md\r
    ↓\r
Present session summary\r
    ↓\r
Project state saved for next AI\r
```\r
\r
## Important Notes\r
\r
- Always use absolute paths when referencing `Docs/` directory\r
- Append to `COMPLETED_JOBS.md` (never overwrite previous entries)\r
- Overwrite `NEXT_STEPS.md` each session (it's for the immediate next session)\r
- Preserve historical information in `PROJECT_STATUS.md` and `COMPLETED_JOBS.md`\r
- When in doubt, write more context, not less\r
- This skill supports both English and Chinese trigger phrases for flexibility\r