Results for “work-in-progress”

Implement chat-based user interface with selectable options, progressive disclosure, and workflow guidance for discipline-specific operations including procurement, civil engineering, and other domain workflows

Manage Migration entities — pending, in-progress, and applied transitions between upstream source versions. Use when an upstream source bumps version (processkit, a host installer, or a community package), when a user wants to draft a migration plan, when an agent needs to reason about pending migrations, or when working through an in-progress migration.

Orchestrate multi-agent coding tasks via Codex DevFleet — plan projects, dispatch parallel agents in isolated worktrees, monitor progress, and read structured reports.

Provides a canonical facilitation protocol for interactive skills: one step at a time with progress tracking, adaptive recommendations, and interruption handling.

Orchestrate multi-agent coding tasks via Claude DevFleet — plan projects, dispatch parallel agents in isolated worktrees, monitor progress, and read structured reports.

Orchestrate multi-agent coding tasks via Claude DevFleet — plan projects, dispatch parallel agents in isolated worktrees, monitor progress, and read structured reports.

Orchestrate multi-agent coding tasks by dispatching parallel agents in isolated worktrees, monitoring progress, and reading structured reports.

Guiding workflows by decomposing complex tasks (Epics) into Atomic Steps under 15 minutes each, with progress tracking and drift prevention. Use when complex decomposition is needed.

Provides a structured process for creating or updating skills that extend an AI agent's capabilities with specialized knowledge, workflows, and tool integrations.

Orchestrate multi-agent coding tasks via Claude DevFleet: plan projects, dispatch parallel agents in isolated worktrees, monitor progress, and read structured reports.

Progressively refines context retrieval in multi-agent workflows to solve the subagent context problem.

Detects the current state of an Open-workspace project and advances to the next logical workflow step, from discussion through planning, execution, verification, and completion.

Work incrementally on issues using Git worktrees for parallel agent workflows, starting each session by getting bearings and ending with clean state.

Writes or updates a HANDOFF.md document to preserve context for the next agent, including goal, progress, what worked, what didn't, and next steps.

Personal trainer operations: client check-ins, workout-program delivery, progress reminders, session reminders, lead follow-up, and workout tracking. Use when an owner is a coach/personal trainer or when managing fitness clients and training routines.

Compact the current conversation into a handoff document for another agent to pick up. Use when user wants to hand off work, summarize progress, or prepare context for a new session.

Generate one best-next-step proposal after a successful task run, either the next phase in a series or a high-value improvement.

Progress Tracking

Write grant reports with progress, financials, and outcomes. TRIGGERS - Use when user needs help with grant-report related tasks.

Generate one high-value follow-up workflow proposal when MoonMind execution quality issues are detected in a run.

Use to CREATE or REVIEW a Job to be Done (JTBD) in Alan Klement's demand-side, progress-based sense — a job is the progress a customer is trying to make, never a task or feature. Trigger whenever someone wants to write or draft a JTBD, job statement, or job story; figure out the real motivation, struggle, or progress behind a feature, request, or product; understand why customers switch, adopt, or churn; turn interview notes or research into jobs; or pressure-test, sharpen, or rewrite existing JTBDs into proper jobs. Also trigger on "grill my JTBD", "is this a real job or just a task/feature", "what's the actual job here", "why would they switch". In an A-Team target repo, jobs are durable artifacts — this skill writes docs/product/jtbd/NN-<slug>.md per CONTRACT.md and never deletes or silently rewrites a job. Do NOT use for writing PRDs, roadmaps, tickets, or acceptance criteria (those consume a finished JTBD), or for implementation user stories.

Checks project progress, summarizes recent work and what's ahead, then routes to the next action by executing an existing plan or creating a new one.

Design a worked example fading sequence from fully worked examples through to independent practice. Use when teaching procedures, algorithms, or multi-step processes to novice learners.

Guides users through creating effective skills that extend AI coding agents with specialized knowledge, workflows, and tool integrations.

Generates detailed, technology-agnostic implementation blueprints by analyzing project architecture, technology stacks, and data flow patterns.

Iterates through pending development plans in .cursor/plans, implementing tasks, running self-tests, reviewing code, committing locally, and moving completed plans to docs/plans/done.

Check BMAD project progress and get next-step recommendations

Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.

Summarize AFPS product-workflow progress from existing artifacts and recommend the next concrete skill command

Imports external plan files into a GSD-structured project, detecting conflicts against existing roadmap, requirements, and locked decisions before writing a validated PLAN.md.