developer

Automate developer task tracking and progress updates in per-project standup workflows.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/mxnyawi/opencode-standup --skill developer-mxnyawi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: developer
Source: https://github.com/mxnyawi/opencode-standup/tree/main/skills/developer
Command: npx skills add https://github.com/mxnyawi/opencode-standup --skill developer-mxnyawi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developer work often becomes fragmented across projects, leading to lost updates, miscommunication, and inconsistent progress tracking. This skill provides a disciplined framework for developers to log progress, manage tasks, and follow a consistent Git workflow within each project.

Core Features & Use Cases

  • Implement features and fixes with disciplined code quality.
  • Track progress with per-project daily logs and a structured tasks.json.
  • Follow a Git-centric workflow with branch naming, commits, PR processes, and actionable notifications.

Quick Start

Initialize your per-project .standup/developer directory and start your first daily log and task list.

Frequently Asked Questions about developer

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

FAQPage Schema
How do I track developer tasks and daily progress within a project?

Track developer tasks and daily progress by initializing a per-project .standup/developer directory to store daily logs and a structured tasks.json file. This creates a disciplined framework for logging progress, managing features, and maintaining consistent updates across projects.

How does a per-project standup workflow help with bug fixes and feature implementation?

A per-project standup workflow helps with bug fixes and feature implementation by providing a centralized channel for urgent notifications and structured daily logs. This prevents fragmented work, reduces miscommunication, and ensures disciplined code quality across collaboration cycles.

How do I structure a Git workflow for feature implementation and code reviews?

Structure a Git workflow for feature implementation by following consistent branch naming, commit standards, and pull request processes. This skill provides Git-centric guidance to help you ship features and fixes fast while maintaining code quality throughout the collaboration cycle.

Can I manage multiple project task lists without losing updates or context?

Manage multiple project task lists without losing updates by using per-project standup directories. Each project gets its own isolated daily logs and tasks.json file, ensuring progress tracking remains organized, consistent, and independent of other active development work.

What is the best way to automate developer progress updates and urgent notifications?

Automate developer progress updates and urgent notifications by combining a structured tasks.json file with a centralized notifications channel. This approach captures important updates automatically and maintains a reliable record of daily logs within your Git workflow.

Do I need external dependencies to start logging daily standup updates?

No external dependencies are required to start logging daily standup updates. Initialize your per-project .standup/developer directory directly to create your first daily log and task list, enabling immediate task tracking and progress management.