start-task

Create standardized task folders with tracker-aware names and session metadata.

28|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/ma08/botfiles --skill start-task-ma08
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-task
Source: https://github.com/ma08/botfiles/tree/main/hermes/skills/start-task
Command: npx skills add https://github.com/ma08/botfiles --skill start-task-ma08

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually creating task folders, capturing machine and session metadata, linking to project trackers like GitHub or Linear, and setting up consistent artifact storage is tedious and error-prone, leading to lost context and broken cross-session continuity for long-running coding agent workflows.

Core Features & Use Cases

  • Tracker-aware slug generation: Automatically creates task folder names based on GitHub issue numbers or Linear ticket IDs, with stable truncation for long titles.
  • Standardized folder structure: Generates consistent task directories with status.md, user input storage, and separate scratchpad and deliverable artifact spaces.
  • Cross-session context capture: Records machine, coding agent, and session metadata to ensure tasks can be resumed seamlessly across different agent sessions.
  • Use Case: A developer working on a 24/7 coding agent can use this skill to instantly set up a new task for a GitHub issue about fixing a login bug, with all required context and structure ready for the agent to begin work.

Quick Start

Use the start-task skill to create a new tracked task folder for the GitHub issue #456 about implementing the password reset flow.

Frequently Asked Questions about start-task

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

FAQPage Schema
How do I set up task folders for coding agents linked to GitHub issues?

To set up task folders for coding agents linked to GitHub issues, this skill generates tracker-aware folder slugs using issue numbers. It creates a standardized directory structure with status tracking, user input storage, and separate spaces for scratchpad and deliverable artifacts to ensure full lifecycle management.

What is cross-session context capture for long-running agent workflows?

Cross-session context capture records machine, coding agent, and session metadata within task folders. This ensures long-running agent workflows can be resumed seamlessly across different sessions without losing project state or tracker synchronization details.

Can I use this task initialization skill with Linear tickets?

Yes, you can use this skill with Linear tickets. It supports tracker-aware slug generation for both Linear ticket IDs and GitHub issue numbers, applying stable truncation for long titles to maintain consistent task metadata across platforms.

What's the best way to structure artifacts for automated coding workflows?

The best way to structure artifacts for automated coding workflows is using standardized task directories. This skill separates scratchpad spaces from final deliverable artifacts and includes a status file, preventing context loss during long-lived coding agent execution.

Why do I lose context when resuming coding agent tasks across sessions?

You lose context resuming coding agent tasks because manual folder setup fails to capture machine and session metadata. This skill solves the problem by automatically recording cross-session context and linking it directly to project trackers like GitHub or Linear.