AgentSkillsCN

start-action

从行动追踪器中启动一项行动。根据标题搜索匹配的行动,并为协调者提取上下文信息。

SKILL.md
--- frontmatter
name: start-action
description: Start work on an action from the action-tracker. Searches for matching action by title and extracts context for the orchestrator.
user-invocable: true
argument-hint: "[action title or partial match]"

Start Action Workflow

You are starting work on an action from Linear.

Input

Action search: $ARGUMENTS

Prerequisites

This skill requires Linear integration. Ensure LINEAR_API_KEY is set in .env:

bash
# .env
LINEAR_API_KEY=lin_api_xxxxx

Linear Workflow States

StateMeaningWhen to Use
BacklogIdeas, not committedLow-priority ideas
TodoAccepted, ready to startCommitted, waiting to begin
In ProgressCurrently being worked onActive work (including monitoring/validation)
DoneFully completedFinished with outcomes recorded

State IDs (founder advisors team)

code
Backlog:     1f692912-2a27-4e8c-b4e8-77dac00666b2
Todo:        b09856af-f221-495d-8280-cc886cca8255
In Progress: 155b3856-c8ec-41ae-b339-007b7099d51f
Done:        25b69969-5bfa-4885-bf43-f6764a9377d1
Canceled:    33295a98-43af-40c0-9712-649d59f4d0af

Important State Transitions

  • When starting work → Update to In Progress
  • "Released but monitoring" = still In Progress (not Done)
  • Only move to Done when fully complete with no follow-up needed

Step 1: Find the Action

Search for the action in Linear using the CLI tool:

bash
# List all issues (actions)
./tools/linear.sh issues

# Or search in specific project
./tools/linear.sh issues [project_id]

Find the action that best matches "$ARGUMENTS" (case-insensitive, partial match OK).

Step 2: Extract Action Context

From the matching Linear issue, extract:

  • Title: The issue title
  • Priority: Issue priority (1=urgent, 4=low)
  • Status: Current workflow state
  • Description: Full description with context
  • Identifier: Linear issue ID (e.g., PPT-123)

You can fetch full issue details with:

bash
./tools/linear.sh query "{ issue(id: \"<issue_id>\") { id identifier title description priority state { name } } }"

Step 3: Route to Orchestrator

Use the pocketpal-orchestrator agent with the extracted context:

code
Use pocketpal-orchestrator: [Action Title]

Context from Linear:
- Linear ID: [identifier]
- Priority: [priority]
- Status: [status]

Description:
[description from Linear issue]

Repository: ./repos/pocketpal-ai

What Happens Next

The orchestrator will:

  1. Create a worktree for this action
  2. Classify complexity based on the description
  3. Route to planner to create a story file
  4. Story will include Linear context for traceability

Example

Input: /start-action "lifecycle guard"

Searches Linear issues, finds: "PPT-42: Fix UnknownCppException/SIGSEGV Crashes"

Extracts:

  • Description: Add lifecycle guard to prevent context release during inference
  • Priority: 1 (urgent)
  • Status: In Progress

Routes to orchestrator with full context.

Without Linear API Key

If LINEAR_API_KEY is not set, this skill will not work. You can:

  1. Add your Linear API key to .env
  2. Or use /start-task with a manual description instead