close-shop

Analyzes project data to identify and suggest fixes for workflow inefficiencies.

1|Updated Mar 27, 2026

Search Tags:#automation #workflow #github #analysis #retrospective #plugin

Ready to run

npx skills add https://github.com/steve-piece/bytheslice --skill close-shop

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: close-shop
Source: https://github.com/steve-piece/bytheslice/tree/main/skills/close-shop
Command: npx skills add https://github.com/steve-piece/bytheslice --skill close-shop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill addresses the lack of continuous improvement in agentic workflows by analyzing execution history to identify systemic friction patterns and drafting targeted improvements.

Core Features & Use Cases

Friction Analysis: Automatically reviews stage logs, git history, and human-in-the-loop escalations to find bottlenecks.
Automated Improvement: Drafts draft pull requests against the plugin repository to refine prompts, skills, and references.
Use Case: After completing a complex project, run this skill to debrief the shift, identify why certain stages required multiple passes, and propose updates to the plugin to prevent those issues in the next project.

Quick Start

Invoke the close-shop skill to review the last three stages of the current project and draft a pull request for any identified workflow improvements.

Frequently Asked Questions about close-shop

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

FAQPage Schema

How do I automate post-project retrospectives for agentic workflows?▼

Automated post-project retrospectives analyze project execution logs and git history to detect systemic friction patterns, identifying bottlenecks in skill execution and agent performance. This process generates actionable improvement proposals to refine prompts and references.

What is the best way to analyze git history for workflow bottlenecks after a project?▼

Analyzing git history for workflow bottlenecks requires reviewing stage logs and human-in-the-loop escalations to detect friction patterns. The analysis drafts targeted improvements and generates pull requests against the plugin repository to prevent recurring issues.

Do I need the GitHub CLI to run friction analysis on agent performance?▼

Yes, detecting systemic friction patterns in agentic workflows requires integration with the GitHub CLI. Accessing project-specific execution metadata and git history through the CLI is necessary to draft automated improvement pull requests for plugin maintenance.

How does an automated retrospective identify systemic friction in skill execution?▼

Automated retrospectives identify systemic friction by reviewing project execution logs, git history, and human-in-the-loop escalations. This mechanism finds stages requiring multiple passes and drafts pull requests to refine prompts, skills, and references for future projects.

Can I use workflow analysis to automatically draft pull requests for plugin maintenance?▼

Yes, workflow analysis can automatically draft pull requests for plugin maintenance. By detecting friction patterns in execution logs and git history, it generates targeted code improvements to refine prompts and references directly in the repository.

When should I run an automated after-service retrospective on my project?▼

You should run an automated after-service retrospective after completing a complex project or during plugin maintenance cycles. It reviews recent stage logs to debrief the shift, identify why stages required multiple passes, and propose updates to prevent future bottlenecks.