---
title: "qol-sessions"
description: "Architect-to-implementer feature loop for independent terminals."
canonical: https://agentpluginsdirectory.com/plugins/qol-sessions
last-updated: 2026-10-02
---

# qol-sessions
Architect-to-implementer feature loop for independent terminals.
- Slug: qol-sessions
- Publisher: KMRH47
- Repository: https://github.com/qol-tools/qol-skills
- Manifest: plugins/qol-sessions/plugin.json
- Category (editorial): productivity
- Skills: 3 (architect, fork, qol-sessions)
- MCP servers: 1 (qol-sessions)
- Stars: 0
- Repository created: 2026-08-21
- Repository last pushed: 2026-09-30
- Publisher type: Organization
- Listing: https://agentpluginsdirectory.com/plugins/qol-sessions
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What qol-sessions does, in the publisher's words

Claude Code, Codex, and Kimi Code skills marketplace for the qol-tools org.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/qol-tools/qol-skills/HEAD/README.md

## Skills

- architect: Run one task as the planning-only architect. Use when the user invokes /architect <task>. The architect scopes, scouts through lanes, writes the spec, fans out lanes, reviews, runs the single gate, and accepts; it never implements.
- fork
- qol-sessions: Use when an architect must create or drive an implementation agent in another terminal through event-signalled implementation and review rounds until a feature is accepted. Also use for cross-terminal handoffs, relays, bridges, or independent agent sessions. The agent surface is sessions_list, sess…

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.

## MCP servers

- qol-sessions: transport: stdio; command: qol sessions mcp

Read from the plugin's own mcp.json. Environment variable names only, never values.