daily-task-start

Load task context, explore codebase files, and propose an implementation plan.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of starting a task by providing comprehensive context and a clear implementation plan.

Core Features & Use Cases

  • Task Initialization: Initiates tasks with detailed context including task details, notes, and previous progress.
  • Codebase Exploration: Identifies relevant files and recent changes related to the task.
  • Implementation Plan: Proposes a structured plan for task completion and awaits user approval.

Quick Start

Start the task with ID 'ENG-123' from today's plan by typing: /daily-task-start ENG-123

Frequently Asked Questions about daily-task-start

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

FAQPage Schema
How do I start a task execution with a clear implementation plan?

To start task execution with an implementation plan, load relevant context, explore codebase files, and propose a structured plan that requires user confirmation before proceeding.

What is the best way to load context and explore codebase files for a new task?

The best way to load context for a new task is to use a task initiation script that identifies relevant files, checks recent codebase changes, and aggregates task details with previous progress notes.

Can I propose an implementation plan and wait for approval before modifying code?

Yes, you can propose an implementation plan and wait for approval before modifying code, as the task initiation process requires user confirmation before proceeding with execution.

Does task initiation work within a daily planning context for software engineering?

Task initiation works within a daily planning context for software engineering by structuring task management, pulling task IDs from today's plan, and preparing the necessary context for execution.

What context is loaded when I start task execution?

When you start task execution, the context loaded includes task details, previous progress notes, relevant codebase files, and recent changes related to the specific task ID.