Skill
/tasklist
Permanent task IDs, ownership, and lifecycle history
What it does
/as:tasklist owns the canonical TASKS.md for a project, or a studio-wide portfolio register if you opt into one.
Every task carries a permanent ID that survives edits and reordering, an owner, lifecycle dates, and a link back to the artifact it came from — the meeting, the site report, the plan.
What it does not do
It does not plan the work. That’s /as:workplan.
It also does not turn every proposed action into a task. Action candidates surfaced by minutes and site reports stay candidates until you promote them. A list that fills itself is a list nobody trusts.
Install
Claude Desktop:
- Open Customize → Browse plugins
- Click + → Add marketplace from GitHub
- Enter
AlpacaLabsLLC/skills-for-architects - Install Architecture Studio
Claude Code (terminal):
claude plugin marketplace add AlpacaLabsLLC/skills-for-architects
claude plugin install as@skills-for-architects
Usage
/as:tasklist ← list open tasks
/as:tasklist add ← add a task
/as:tasklist update ← change owner, dates, or status
/as:tasklist complete ← close a task, keeping its history
/as:tasklist cancel ← cancel a task, keeping its history
In a studio workspace with portfolio mode enabled, it reads across every registered project.