developer

Translate change requests into tracked tasks and orchestrate coder agents.

2|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/potenlab/marketplace-potenlab --skill developer-potenlab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: developer
Source: https://github.com/potenlab/marketplace-potenlab/tree/main/plugins/potenlab-workflow/skills/developer
Command: npx skills add https://github.com/potenlab/marketplace-potenlab --skill developer-potenlab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-completion development changes can be error-prone and manual. This Skill translates change requests into tracked tasks and coordinates parallel coding efforts, ensuring a reproducible audit trail.

Core Features & Use Cases

  • Change translation: Converts user requests into concrete tasks recorded in docs/changes.json.
  • Context-aware planning: Reads progress.json, dev/frontend/backend plans, and existing code to scope changes correctly.
  • Parallel execution: Spawns small-coder and high-coder agents in parallel to implement tasks and updates the changes log.
  • Auditability: Generates status updates and reports results to stakeholders, preserving a complete history.

Quick Start

Invoke /developer with a concise change description to start a new change batch.

Frequently Asked Questions about developer

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

FAQPage Schema
How do I automate post-launch change requests and track them?

To automate post-launch change requests, this skill translates change descriptions into concrete tracked tasks, updates docs/changes.json, and orchestrates parallel coding agents to implement the modifications while maintaining a full audit trail.

How does agent orchestration work for software engineering tasks?

Agent orchestration works by reading existing project plans and code to scope changes, then spawning small-coder and high-coder agents in parallel to execute tasks, automatically updating the progress tracking logs and reporting results to stakeholders.

What is the best way to ensure auditability when applying post-completion code fixes?

To ensure auditability for post-completion code fixes, the system records all adjustments in docs/changes.json and reads progress.json to preserve a complete history, generating status updates that report results back to stakeholders.

Can I use this change management skill to update existing development plans?

Yes, you can use this change management skill to update existing development plans because it is context-aware, reading progress.json, dev/frontend/backend plans, and existing code to correctly scope and implement requested adjustments.

Do I need existing project documentation to coordinate post-launch changes?

Yes, existing project documentation is needed because the skill reads your progress.json, development plans, and existing code base to correctly scope changes, plan the agent execution, and update the changes log accurately.