contextstream-workflow

ContextStream Workflow Skill

Purpose

Use ContextStream to keep plans, tasks, decisions, lessons, and implementation context available across Copilot sessions.

Session Lifecycle

1. Start the session

Always call init at the beginning of a new session:

init(
  folder_path="<project_path>",
  context_hint="<user's first message>"
)

Then call context with the current request:

context(
  user_message="<current user message>"
)

For later messages in the same session, call context first before doing more work.

Before inventing a workflow from memory, check whether ContextStream already surfaced relevant skills, docs, lessons, or decisions for the task. Use skill(action="list"), memory(action="list_docs"), session(action="get_lessons"), and memory(action="decisions", workspace_id="<current_workspace_id>", project_id="<current_project_id>") when ids are available and the task is unfamiliar or likely already documented. Reuse the current project_id returned by init or context for project-scoped docs, events, and skills instead of guessing.

2. Plan multi-step work

Capture a persistent plan:

session(
  action="capture_plan",
  title="Implement feature X",
  steps=[
    {"id": "1", "title": "Research the current code path", "order": 1},
    {"id": "2", "title": "Implement the change", "order": 2},
    {"id": "3", "title": "Add verification", "order": 3}
  ]
)

Then create linked tasks:

memory(
  action="create_task",
  title="Implement the change",
  plan_id="<plan_id>",
  plan_step_id="2",
  priority="high"
)

3. Track progress while working

Start a task:

memory(
  action="update_task",
  task_id="<task_id>",
  status="in_progress"
)

Capture a technical decision:

session(
  action="capture",
  event_type="decision",
  title="Use repository pattern for data access",
  content="Chose a repository layer to isolate persistence logic and simplify testing."
)

Finish a task:

memory(
  action="update_task",
  task_id="<task_id>",
  status="completed"
)