/workplan

What it does

/as:workplan produces a plan sized to the work — inline for most requests, saved as a registered Markdown document when you want it kept — covering scoping, sequencing, and coordination before anything gets built.

It separates what is known from what is assumed, traces every requirement into a work unit you can verify, and stops at an explicit execution handoff rather than starting the work on its own.

This is work planning, and it deliberately stays out of the way of floor plans, site plans, space planning, zoning calculations, and building-code analysis — those belong to the zoning and programming skills.

Project context

In a project with records, the plan reads and cites what already exists — PROJECT.md facts, decision records, meetings, site reports, and tasks.

Decided records constrain the plan. Proposed decisions stay unresolved rather than getting quietly assumed. Superseded decisions remain visible as historical context.

Install

Claude Desktop:

1. Open Customize → Browse plugins
2. Click + → Add marketplace from GitHub
3. Enter AlpacaLabsLLC/skills-for-architects
4. Install Architecture Studio

Claude Code (terminal):

claude plugin marketplace add AlpacaLabsLLC/skills-for-architects
claude plugin install as@skills-for-architects

Usage

/as:workplan

Describe the work and the plan comes back with facts, assumptions, work units, and a handoff. A plan-only request ends at the plan; saving it doesn’t import tasks or start the work.