Agent Skill: Project Start

Project-start automation is useful when it turns a loose task into a named branch, a short plan, and explicit next steps.

Adarsh Trivedi · August 20, 2025 · 2 min read

Takeaway: The value is not ceremony. It is reducing drift before implementation begins.

What it does

This skill takes a task description or existing ticket and sets up the working lane: ticket context, branch naming, and a small implementation outline.

The public idea is simple: start with a stable reference and a branch that explains the work. Keep the operational details private and environment-specific.

Why it helps

It prevents the first half hour of a task from becoming scattered setup. It also makes handoff easier because the branch, task, and plan share the same intent.

Sanitized skill notes

This is the public version of the saved skill markdown. I replaced tracker names, project keys, branch conventions, and API details with placeholders.

name: project-start
purpose: Turn a task or existing ticket into a ready working lane.

workflow:
  1. Detect whether the prompt references an existing ticket.
     - if yes, fetch or summarize its intent
     - if no, draft a short ticket summary and description for approval

  2. Create or confirm the work item.
     Use the team's tracker and status flow.

  3. Create a feature branch.
     Suggested shape: [ticket-key]-[short-task-slug]

  4. Suggest implementation changes.
     - affected areas
     - likely files
     - data or API boundaries
     - checks to run

  5. Save a short plan.
     Keep the plan close to the work so future sessions can resume safely.