Initial commit

This commit is contained in:
Zhongwei Li
2025-11-30 08:56:18 +08:00
commit c50d9b355d
7 changed files with 541 additions and 0 deletions

102
commands/context-restore.md Normal file
View File

@@ -0,0 +1,102 @@
Restore context from ConPort and ClickUp using the intelligent context-manager agent.
Use the Task tool to launch the context-manager agent with the following prompt:
"Restore project context from ConPort and ClickUp. Provide an intelligent briefing with ConPort decisions, active ClickUp tasks, time tracking summary, and synthesized next actions."
---
## Manual Mode (if agent unavailable)
If you need to restore context manually, follow these guidelines:
### What to load from ConPort
### 1. Product Context (`mcp__conport__get_product_context`)
Load project overview:
- Project name, description, goals
- Technology stack
- Core features and architecture
- Current project status
### 2. Active Context (`mcp__conport__get_active_context`)
Load current work state:
- Current focus and session summary
- Recent completed tasks and files changed
- Next steps and planned work
- Current branch and uncommitted changes
- Any blockers
### 3. Recent Decisions (`mcp__conport__get_decisions`)
Retrieve last 5-10 architectural decisions:
- Decision summaries and rationale
- Implementation details
- Relevant tags for filtering
### 4. Recent Progress (`mcp__conport__get_progress`)
Check task progress:
- Recently completed tasks
- In-progress items
- Pending work
### 5. Recent Activity Summary (`mcp__conport__get_recent_activity_summary`)
Get overview of last 24-48 hours:
- New decisions, progress entries
- Context updates
- System pattern changes
### 6. ClickUp Tasks (Optional)
Load task management context:
**Search Active Tasks:**
- Use `mcp__clickup__searchTasks` with `assigned_to_me: true`
- Filter by `only_todo: true` to see open tasks
- Get task priorities and statuses
**Get Recent Time Entries:**
- Use `mcp__clickup__getTimeEntries` to see what was worked on recently
- Understand time allocation and focus areas
**Load Task Details:**
- Use `mcp__clickup__getTaskById` for important tasks
- Read comments for recent updates and discussions
**Search Related Spaces:**
- Use `mcp__clickup__searchSpaces` to understand project structure
## Output Format
After loading all context, provide:
**[CONPORT_ACTIVE]** status indicator
### Project Status
- Brief project description
- Current phase/milestone
### Where We Left Off
- Last session's focus and accomplishments
- Files created/modified
- Key decisions made
### Recent Decisions (last 7 days)
- List important architectural/implementation decisions
### Current State
- Active branch
- Uncommitted changes
- Open tasks or blockers
### ClickUp Tasks (if available)
- Active tasks with status and priority
- Recent time tracking summary
- Task links: https://app.clickup.com/t/TASK_ID
- Upcoming deadlines or blockers
### Next Steps
- Suggested actions based on active_context and ClickUp tasks
- Prioritized list combining ConPort and ClickUp data
- Ask: "Continue previous work?" or "What should we work on?"
## Example Usage
Run this command at the start of a session to quickly understand project state from both ConPort (decisions, context) and ClickUp (tasks, time tracking) and continue where you left off.

71
commands/context-save.md Normal file
View File

@@ -0,0 +1,71 @@
Save current context to ConPort and ClickUp using the intelligent context-manager agent.
Use the Task tool to launch the context-manager agent with the following prompt:
"Analyze the current session and save comprehensive context to ConPort and ClickUp. Include conversation analysis, git changes, decisions made, next steps, and create/update ClickUp tasks as needed."
---
## Manual Mode (if agent unavailable)
If you need to save context manually, follow these guidelines:
### What to save to ConPort
### 1. Update Active Context (`mcp__conport__update_active_context`)
Create a comprehensive snapshot with:
- **current_focus**: Brief description of what you're working on
- **session_summary**: Summary of work done in this session
- **recent_work**: Object containing:
- `completed_tasks`: Array of completed tasks
- `files_created`: Array of new files with brief descriptions
- `files_modified`: Array of modified files with changes
- `key_findings`: Important discoveries or insights
- **next_steps**: Array of planned next actions
- **current_branch**: Git branch name
- **uncommitted_changes**: Array of files with uncommitted changes
- **blockers**: Any issues or blockers (if applicable)
### 2. Log Decisions (`mcp__conport__log_decision`)
If architectural or implementation decisions were made:
- **summary**: Concise decision summary
- **rationale**: Why this decision was made
- **implementation_details**: How it will be/was implemented
- **tags**: Relevant categorization tags
### 3. Log Progress (`mcp__conport__log_progress`)
For each completed task:
- **status**: DONE, IN_PROGRESS, or TODO
- **description**: Task description
- **linked_item_type** and **linked_item_id**: Link to related decisions if applicable
### 4. Update TodoWrite State
Check current todos and save their state to active_context if relevant.
### 5. ClickUp Integration (Optional)
Enhance context persistence with task management:
**Search for Related Tasks:**
- Use `mcp__clickup__searchTasks` to find existing tasks related to current work
- Check task status and update if work was completed
**Create Tasks from Next Steps:**
- Use `mcp__clickup__createTask` for action items from next_steps
- Include links to ConPort decisions in task descriptions
- Format: `Related decision: [decision_id]`
**Update Task Progress:**
- Use `mcp__clickup__updateTask` to reflect completed work
- Add status transitions (e.g., TODO → IN_PROGRESS → DONE)
**Add Progress Comments:**
- Use `mcp__clickup__addComment` to document what was accomplished
- Include links to relevant files or decisions
- Format: `Completed: [description]. Related: https://app.clickup.com/t/TASK_ID`
**Log Time Entries:**
- Use `mcp__clickup__createTimeEntry` for time tracking
- Include description of work done
## Example Usage
After completing a feature, fixing bugs, or before `/compact` or `/clear`, run this command to ensure all work is preserved in ConPort and optionally tracked in ClickUp for future sessions.