start-task

Search for a Trekker task, restore context, and set status to in_progress.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/obsfx/trekker-codex --skill start-task-obsfx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-task
Source: https://github.com/obsfx/trekker-codex/tree/main/skills/start-task
Command: npx skills add https://github.com/obsfx/trekker-codex --skill start-task-obsfx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams begin Trekker tasks efficiently by performing a search to locate the correct task, restoring previous context to prevent context loss, and moving the task into an in_progress state when ready.

Core Features & Use Cases

  • Search-first discovery: find the correct task by keyword and review related context.
  • Context restoration: load previous history and comments to inform the new work session.
  • Dependency awareness: surface blockers and dependencies before starting work.
  • State transition: mark the task as in_progress once readiness is confirmed.

Quick Start

Search for the target task, review its history and blockers, then update its status to in_progress.

Frequently Asked Questions about start-task

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I restore context and resume a tracked task without losing previous history?

To restore context for a tracked task, you can search for the task by keyword, review its previous history and comments, and then update the status to in_progress to resume work.

What is the best way to start work on a tracked task and check for blockers?

The best way to start a tracked task is to perform a keyword search, review the task history, list any existing blockers or dependencies, and finally transition the task status to in_progress.

How does task context recovery work across different work sessions?

Task context recovery works by searching for the target task and loading its previous history and comments before starting work, ensuring that context is preserved and visible across sessions.

Can I update task status to in_progress before reviewing task dependencies?

No, the sequence is deterministic: you must search, show the task, review history, and list blockers before setting the task status to in_progress to ensure dependencies are visible.

Do I need to manually search for task blockers before starting work?

You do not need to manually search for blockers; the task starting sequence automatically surfaces blockers and dependencies before you confirm readiness and transition the status to in_progress.