/master-schedule

What it does

Type /as:master-schedule when a project’s FF&E schedule should become a record. Claude adopts the items you select into permanent records under ffe/items and ffe/schedules, then reads, revises, reconciles, snapshots, exports, or recovers them on request.

Every item keeps a permanent ID that survives retagging and retries. Revisions are sequential and never rewritten, and each schedule revision pins the exact item revisions it contains, so a later change to an item never silently updates another schedule.

Adoption is always explicit. A workbook you hand it does not adopt anything, and a one-off workbook task needs no project setup. Stale revisions, unexplained pending state, or a broken chain stop the operation rather than being repaired.

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

Or symlink just this skill:

git clone https://github.com/AlpacaLabsLLC/skills-for-architects.git
ln -s $(pwd)/skills-for-architects/skills/master-schedule ~/.claude/skills/master-schedule

Usage

/as:master-schedule

Record work runs inside a project: the skill resolves the exact project first and previews unresolved mappings or conflicts before asking for anything it actually needs.

Records and revisions

Each change follows one sequence: inspect, prepare, verify the preparation, apply, verify the result, complete. The full set — every new item revision plus the complete schedule revision — is prepared and checked before the first file is published, and the result is reread in full before the skill reports it done.

Earlier revisions and other schedules’ pinned items are always preserved. If something goes wrong partway, the pending state stays visible rather than being reported as finished.

Workbooks are views

Once a schedule is adopted, the records own the specifications and a workbook is a pinned editing or presentation view. Before editing one, the skill keeps a native backup and reads real values, formulas, link targets, and structure. Incoming edits are reconciled against the base and current revisions, and conflicts are shown for review instead of overwritten. A CSV is not treated as a substitute for the workbook.

Export and recovery always create a new file. Restoring an older view never rolls back the current specifications.

Pairs with

Other skills can propose items, and the reusable product-library.csv belongs to product-library — only this skill adopts or revises schedule records:

• /as:product-research — find products from a design brief
• /as:product-spec-bulk-fetch — extract specs from product page URLs
• /as:product-spec-pdf-parser — extract specs from PDF catalogs
• /as:product-data-import — normalize an existing product list for intake
• /as:product-enrich — auto-tag categories, colors, and materials