skills.rest
edobry
edobryCOMMUNITY
Explore all skills by this author →
𝕏@_gingervitizGitHub

implement-task

Automate end-to-end task implementation from spec to PR in Minsky sessions.

6|1|Updated Apr 26, 2025
Search Tags:#testing#pr#session#implement#task#minsky
One-click install
npx skills add https://github.com/edobry/minsky --skill implement-task-edobry
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement-task
Source: https://github.com/edobry/minsky/tree/main/.claude/skills/implement-task
Command: npx skills add https://github.com/edobry/minsky --skill implement-task-edobry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, end-to-end lifecycle for implementing a Minsky task entirely within isolated session workspaces, reducing context switching and ensuring traceability from spec to PR.

Core Features & Use Cases

  • End-to-end task lifecycle: read the spec, plan, code, test, verify, commit, and create a PR all within a session workspace.
  • Absolute path operations: all file interactions use absolute paths under the session directory to prevent accidental edits to the main workspace.
  • Guided collaboration and validation: supports structured verification and PR creation to align with team workflows.

Quick Start

Start a Minsky session, read the task spec, implement the changes, run tests, and open a PR when ready.

Frequently Asked Questions about implement-task

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

FAQPage Schema
How do I automate end-to-end task implementation within an isolated development session?▼

End-to-end task implementation within an isolated session automates the lifecycle from reading the spec to coding, testing, and creating a PR. This prevents context switching by keeping all file interactions within a dedicated session workspace.

What is the best way to ensure traceability from a task spec to a pull request?▼

Ensuring traceability from a task spec to a PR requires a structured workflow that reads the specification, implements changes, runs tests, and opens a PR. This lifecycle guarantees development aligns with the original requirements.

How do I prevent accidental edits to the main workspace during task implementation?▼

Preventing accidental edits during task implementation requires using absolute path operations under a dedicated session directory. This isolates all file interactions, ensuring the main workspace remains untouched during development and testing.

Does session-based task implementation support structured verification before opening a PR?▼

Session-based task implementation supports structured verification by requiring spec verification and running tests before creating a PR. This guided validation ensures code changes meet the required standards before collaborative review.

Can I manage planning, coding, and testing all within a single Minsky session?▼

Yes, you can manage planning, coding, and testing within a single Minsky session. The end-to-end task lifecycle spans these development phases entirely in session-scoped workspaces, reducing context switching and ensuring reliable delivery.

Related Skills

Explore More Software Engineering Skills→
cyzuscyzus
62

filesystem-skill

Manage workspace files across host and sandbox execution modes.

Community
Intermediate
coco-researchcoco-research
264

gsd-ship

Push a verified branch and create a merge-ready pull request.

Community
Advanced
acta0724acta0724

verification-loop

Automates multi-phase code quality verification including builds, linting, and testing before pull request creation.

Community
Intermediate
memorysavermemorysaver

aep-build

Automates feature implementation workflows in isolated Git worktrees on feature branches.

Community
Advanced