twl:co-architect

Name: twl:co-architect
Availability: InStock
Author: shuu5

Coordinate architecture design tasks with issue-linked exploration and PR-based approvals.

Updated Apr 5, 2026

Search Tags:#workflow #architecture #documentation #review #branch #issue #pr

Ready to run

npx skills add https://github.com/shuu5/twill --skill twl-co-architect

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: twl:co-architect
Source: https://github.com/shuu5/twill/tree/main/plugins/twl/skills/co-architect
Command: npx skills add https://github.com/shuu5/twill --skill twl-co-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

対話的アーキテクチャ構築 → branch/PR + workflow-arch-review 経由マージ。Issue 化は co-issue に委託。explore-summary リンク付き Issue を入力として開始。Non-implementation controller（chain-driven 不要）。

Core Features & Use Cases

Stepwise context collection via guided tasks and worktree management.
Worktree creation, exploration, and architecture discovery with DDD concepts.
PR-based review workflow and automated architecture documentation generation.

Quick Start

Start by opening a new co-architect session with an issue containing an explore-summary and follow the guided steps to collect context, create a worktree, and generate architecture docs.

Frequently Asked Questions about twl:co-architect

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

FAQPage Schema

How do I manage architecture design tasks with branch-driven workflows?▼

Architecture design tasks are managed by linking exploration to issues, creating worktrees, and enforcing structured steps that produce documentation and PR-based approvals. This ensures full traceability from context collection to final review.

Can I use PR-based review workflows for collaborative architecture documentation?▼

PR-based review workflows generate automated architecture documentation and require PR-based approvals for merging. This coordinates collaborative projects by enforcing structured steps and completeness checks before integration.

What is the best way to start an interactive architecture session?▼

Start an interactive architecture session by providing an issue containing an explore-summary link. Follow the guided steps to collect context, create a worktree, and generate architecture docs.

Does branch-driven architecture design require a SKILL.md frontmatter?▼

Branch-driven architecture design requires a SKILL.md frontmatter with name and description fields. Optional scripts, references, and assets can be included to support the structured workflow steps.

How does worktree creation support DDD architecture discovery?▼

Worktree creation supports DDD architecture discovery by isolating exploration tasks within dedicated branches. This allows stepwise context collection and structured architecture documentation generation without affecting the main codebase.

When should I not use an interactive architecture design workflow?▼

Interactive architecture design workflows should not be used for implementation tasks or chain-driven processes. It functions as a non-implementation controller focused on architecture documentation, completeness checks, and PR creation.