skills.rest
Vimurai
VimuraiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

arch-task

Closes completed architect P-## tasks, logs completion, and hands off to the Engineer.

Updated Feb 26, 2026
Search Tags:#workflow automation#mcp#handoff#blueprint#architect#task lifecycle#ai-os
One-click install
npx skills add https://github.com/Vimurai/ai-os --skill arch-task-vimurai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: arch-task
Source: https://github.com/Vimurai/ai-os/tree/main/.claude/skills/arch-task
Command: npx skills add https://github.com/Vimurai/ai-os --skill arch-task-vimurai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Architect planning sessions often end without formally closing P-## tasks, leaving TASKS.md stale and the Engineer without a clear signal to start implementation. This Skill enforces a disciplined closure workflow so no architect task is left open without a blueprint, corresponding E-## tasks, and a logged handoff. ## Core Features & Use Cases - Completion Gate Enforcement: Verifies blueprints exist in .ai/blueprints/, E-## tasks are written, and decisions are recorded before marking any P-## task DONE. - Task Status Synchronization: Updates task status through the task-synchronizer-mcp server and appends a dated entry to .ai/LOG.md. - Mandatory Engineer Handoff: Triggers the ai-handoff skill, which writes .ai/COMM.md and emits the handoff_control bridge signal so the Engineer's tmux pane wakes automatically. - Use Case: After finishing a blueprint for a new API module, invoke this Skill to close P-03, log the design summary, and automatically notify the Engineer that E-## implementation tasks are unblocked. ## Quick Start Close the completed architect task P-03, log the blueprint summary, and hand off control to the Engineer.

Frequently Asked Questions about arch-task

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

FAQPage Schema
How do I mark an architect task as done in AI-OS?▼

Mark a P-## task DONE by calling the task-synchronizer-mcp update_task_status tool with the task id, DONE status, and a one-line summary. Only do this after the blueprint is written, E-## tasks exist in TASKS.md, and any architectural decision is recorded.

How does the architect-to-engineer handoff work?▼

The handoff runs through the ai-handoff skill, which writes .ai/COMM.md and emits a handoff_control bridge signal. The ai watch tmux watcher detects this signal and wakes the Engineer's pane automatically, so no manual keypress is needed.

What must exist before closing a P-## task?▼

Four conditions are required: a blueprint in .ai/blueprints/ or .ai/architect.md, corresponding E-## tasks written to TASKS.md, a decision-recorder entry for any architectural decision, and no open questions in the blueprint.

Can the architect task closure modify source code?▼

No. The skill explicitly forbids modifying source code or any files outside .ai/ and plans/. Its scope is limited to task status updates, log entries in .ai/LOG.md, and triggering the engineer handoff.

What happens if the handoff step is skipped?▼

Skipping the handoff breaks the autonomous ping-pong loop between Architect and Engineer. COMM.md alone orients the Engineer, but only the handoff_control bridge signal wakes the Engineer's tmux pane, so the step is mandatory per rule E-119.

Related Skills

Explore More Software Engineering Skills→
Gentleman-ProgrammingGentleman-Programming
1.3k

sdd-tasks

Translate change proposals and specs into phased tasks.md files with checkboxes.

Official
Intermediate
wise-clawwise-claw
10

trellis-check

Verify code changes against quality standards and project specifications before commits.

Official
Advanced
TeiNamTeiNam
12

architecture-decision-records

Record architectural decisions with context, alternatives, and consequences.

Community
Advanced
bdsqqqbdsqqq
59

tmux

Manage background processes in tmux windows with commands.

Community
Intermediate