Macstack Dev

Plugin macstack-dev in Agents-Store/codex-plugins. Commands read from the repo's manifest — 6 days ago.

Skills (26)

• best-practices

  This skill should be used when the user asks to "install best practice rules", "set up project rules", "add project rules and commands", "set up project conventions", or scaffold-project reaches the rules step. Installs the proven MACSTACK rule set (.claude/rules) and core slash-command skills (.cla

• check

  Validate the spec and the documents, report where the project stands and what to run next, or audit the implementation against the documents Arguments: [--docs | --code | --new | (empty = spec + documents + dashboard)].

• client-package

  This skill should be used when the user asks to "send the documents to the client", "give the client something to comment on", "собрать пакет для клиента", "отдать клиенту на согласование", "показать клиенту артефакт", or needs either half of the client loop — turning the six client documents into o

• code-audit

  This skill should be used when the user asks "what is in the code that the documents do not know about", "сверь код с документами", "обнови документы по коду", "изучи код и найди несоответствия", "the docs are out of date, read the code", or runs /macstack-dev:check --code on a project whose macstac

• conformance

  This skill should be used when the user asks to "check the implementation against the documents", "audit the platform", "does the code do what the spec says", "test the whole stack against the requirements", "conformance review", "what is actually built", or runs /macstack-dev:check --code. Produces

• documents

  This skill should be used when the user asks to "create the macstack folder", "set up project docs", "where do user cases live", "add a screen", "add a trigger", "standardize the project documents", "repair the macstack folder", "migrate docs into macstack", mentions `macstack/`, OVERVIEW, USER-CASE

• feedback

  Report a problem with macstack-dev, the macstack.json schema, or the registry — and fix it at the source Arguments: <what went wrong>.

• feedback

  This skill should be used when the user reports a problem with macstack-dev or the MACSTACK standard — "this skill did the wrong thing", "the schema is missing a field", "the passport for X is wrong", "send macstack feedback", "improve the schema based on my edit", "fix the macstack plugin" — and th

• infisical-env

  This skill should be used when the user asks to "set up Infisical for this project", "create .infisical.json", "pull the env keys", "wire the env", "sync secrets", or scaffold-project reaches the env step. Creates .infisical.json, pulls .env.prod/.env.dev, ensures every key from macstack.json resour

• intake

  Take in anything the client sends — a document, a returned review package, or a correction typed straight into this chat — and merge it through delta → ruling → apply Arguments: [file in inbox/ | what to change, in your own words | (empty = whatever is unprocessed)].

• intake

  This skill should be used when the user says "client sent edits", "merge client feedback", "клиент прислал правки", "разобрать правки", "improve the user cases", "new spec from the client", "process the inbox", "what changed in the client's document", "apply the delta", pastes new client material in

• journal

  This skill should be used when the user wants to "write a changelog", "log what I did", "record today's work", "what shipped", "что сделали", "лог разработки", "записать в журнал", "release notes", "what changed for the client", "закрыть веху", "cut a release" — or whenever ANY document under `macst

• lint

  This skill should be used when the user asks to "validate macstack.json", "lint macstack", "check the stack spec", "verify macstack.json integrity", "check the documents", "where are we", "what should I do next", "project status" — and after any skill of this plugin writes or edits macstack.json or

• plan

  Turn requirements nobody scheduled into well-described tasks, edit tasks and milestones, and reconcile TASKS.md with the team''s own tracker Arguments: [add <what> | sync | status | milestone <id> | (empty = find unplanned work)].

• planning

  This skill should be used when the user asks to "add a task", "what's left to do", "что осталось сделать", "завести задачу", "план работ", "backlog", "milestone status", "sync tasks with the tracker", "синхронизировать задачи", "what should I work on next", "какая веха дальше", "add to the backlog",

• reconcile

  Sync the code and every document in one declared direction — the code is master and the documents get corrected, or the documents are master and the gaps become tasks Arguments: --master=code | --master=docs [--dry] [--only <documents>].

• reconcile

  This skill should be used when the user asks to "sync the code and the documents", "синхронизировать код и документы", "актуализировать документы по коду", "обнови документы, код ушёл вперёд", "bring the documents up to date with the code", "make the code match the documents", "everything has drifte

• review

  Give the client the documents to read and answer — a self-contained HTML file, a published page, or both — and take their answers back Arguments: [--read | --artifact | --only <sections> | --skip <sections> | (empty = the whole package)].

• scaffold-project

  This skill should be used when the user asks to "scaffold the project from macstack.json", "create the project working files", "generate project files from the spec", "build the project from macstack.json", or after a macstack.json is validated and the working tree must be built. Creates project fil

• setup

  This skill should be used when the user asks "what is macstack.json", "set up macstack", "check macstack setup", "verify macstack.json", "explain the macstack standard", or before any other macstack-dev skill runs in a project for the first time. Explains the standard, locates the schema and categor

• spec-authoring

  This skill should be used when the user asks to "create macstack.json", "add macstack.json to this project", "init macstack", "generate macstack.json from scratch", "design a stack for…", "pick software and architecture for my need", "describe this existing project as a spec", "find plugins for this

• start

  Create or repair a project''s macstack/ folder and macstack.json — from nothing (a six-question interview), from an existing macstack.json, from an existing codebase, or by migrating an older layout Arguments: [project path | business request | (empty = design from scratch) | --migrate].

• sync

  This skill should be used when the user says "sync the spec", "the client corrected the roles", "the spec and the documents disagree", "update macstack.json after the code changed", "reconcile the spec with reality", when lint reports rule 12.22, after anyone edits AUTOMATION.md or UX-UI.md, and as

• test-cases

  This skill should be used when the user asks to "make test cases", "составить тест-кейсы", "generate tests from the user cases", "как это проверять", "написать сценарии проверки", "acceptance checklist", "what do we test for C-04", "обновить тест-кейсы под новую версию кейсов", or wants a QA/accepta

• troubleshoot

  Diagnoses failures of the macstack-dev toolchain. Covers lint errors, prototypes that do not resolve or clone, Infisical profile and missing or wiped env keys, scaffold runs that overwrite files, contradict the architecture or leave env references unresolved, macstack/ folder faults (duplicate macst

• update

  Close the loop after work — bring the client documents, the spec and the generated documents up to what the code now does, move task statuses to what the audit found, journal the work and curate the changelog Arguments: [--after M11-T9 | --release M11 | --dry | (empty = every task finished since the

Hooks (2)

• SessionStart

  python3 "${CLAUDE_PLUGIN_ROOT}/hooks/session-start-macstack-stale.py"

• Stop

  python3 "${CLAUDE_PLUGIN_ROOT}/hooks/stop-macstack-stale.py"

Similar plugins