How do I install the Restaurantpos Workstream Orchestrator skill?

Run npx skillmds@latest add tomevault-io/restaurantpos-workstream-orchestrator in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Restaurantpos Workstream Orchestrator safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Restaurantpos Workstream Orchestrator?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Restaurantpos Workstream Orchestrator free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Restaurantpos Workstream Orchestrator?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Restaurantpos Workstream Orchestrator by tomevault-io

Name: Restaurantpos Workstream Orchestrator
Author: tomevault-io

Restaurantpos Workstream Orchestrator

Plan and split RestaurantPOS hardening into safe, reviewable Codex workstreams with minimal shared-file collisions. Use when Codex needs to break a large request into parallel or sequential batches, assign scope boundaries, protect shared files, pick verification depth, or produce batch reports that follow the repo's AGENTS.md. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

RestaurantPOS Workstream Orchestrator

Read AGENTS.md, .codex/AGENTS.md, and references/paths.md before planning or executing a large batch.

Workflow

Classify the request against the repo priority order before writing code.
Split the work into narrow, reviewable batches that own a small file set and a clear test surface.
Treat routes/api.php, config/booking.php, config/staff_capabilities.php, and database/schema/mysql-schema.sql as shared seams that need extra coordination.
Prefer service-layer implementation batches first, then schema or integration sync, then a final pass for seams and regressions.
End each batch with the required report shape: Intent, Changed files, Added or updated tests, Remaining risks.

Guardrails

Avoid broad refactors and speculative cleanup during orchestration.
Defer large shared-file collisions to a later integration or schema-sync batch when possible.
Keep bootstrap, API contract, and operational gate changes visible instead of burying them inside domain batches.
If there is no Git metadata available, still maintain strict batch boundaries and explicit ownership.

Verify

Run targeted tests per batch, not only one full-suite pass at the end.
Use docs/codex-parallel-agent-prompts.md as the default decomposition map for large hardening asks.
Run an integration-focused test slice after shared seams are touched.

Source: DuongVinh2004/RestaurantPOS — distributed by TomeVault.

---name: restaurantpos-workstream-orchestratordescription: Plan and split RestaurantPOS hardening into safe, reviewable Codex workstreams with minimal shared-file collisions. Use when Codex needs to break a large request into parallel or sequential batches, assign scope boundaries, protect shared files, pick verification depth, or produce batch reports that follow the repo's AGENTS.md. Use when this capability is needed.---# RestaurantPOS Workstream OrchestratorRead `AGENTS.md`, `.codex/AGENTS.md`, and `references/paths.md` before planning or executing a large batch.## Workflow1. Classify the request against the repo priority order before writing code.2. Split the work into narrow, reviewable batches that own a small file set and a clear test surface.3. Treat `routes/api.php`, `config/booking.php`, `config/staff_capabilities.php`, and `database/schema/mysql-schema.sql` as shared seams that need extra coordination.4. Prefer service-layer implementation batches first, then schema or integration sync, then a final pass for seams and regressions.5. End each batch with the required report shape: Intent, Changed files, Added or updated tests, Remaining risks.## Guardrails- Avoid broad refactors and speculative cleanup during orchestration.- Defer large shared-file collisions to a later integration or schema-sync batch when possible.- Keep bootstrap, API contract, and operational gate changes visible instead of burying them inside domain batches.- If there is no Git metadata available, still maintain strict batch boundaries and explicit ownership.## Verify- Run targeted tests per batch, not only one full-suite pass at the end.- Use `docs/codex-parallel-agent-prompts.md` as the default decomposition map for large hardening asks.- Run an integration-focused test slice after shared seams are touched.---> Source: [DuongVinh2004/RestaurantPOS](https://github.com/DuongVinh2004/RestaurantPOS) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions