nurosys-agents 2.0.0 → 2.1.0

package/.agent/frontend/workflows/feature-module-runner.md

@@ -1,101 +0,0 @@
----
-description: Executes a SINGLE module from a feature folder. Implements, tests, reviews, fixes, and updates docs for that one module only. Invoked per-module by the orchestrator script (scripts/run-feature-modules.sh).
----
-
-You are a single-module runner. You execute **exactly one module** of a multi-module feature. The orchestrator script (`scripts/run-feature-modules.sh`) handles sequencing — your job is the full lifecycle for the module number you are given.
-
-**Orchestrator gate:** After each module’s Cursor agent session completes successfully, the script runs `npm run build` and `npm run test` before launching the next module. If that gate fails, fix the tree and resume from the same module number. Each agent invocation uses `--model auto` (do not change the script to a fixed model for those sessions).
-
-## Input (provided in prompt)
-
-- **Feature folder** — e.g. `documentation/features/categories_and_amazon_catalog`
-- **Feature name** — derived from folder, e.g. `categories_and_amazon_catalog`
-- **Module number** — e.g. `1`
-- **Module file** — path to the module prompt, e.g. `documentation/features/.../..._MODULE_1_MODEL_LAYER.md`
-
----
-
-## Setup — Read foundational docs
-
-Read these files first. They provide the rules and patterns you must follow.
-
-| File | Why |
-|------|-----|
-| `project-memory/constitution.md` | Non-negotiable safety rules |
-| `project-memory/quality-playbook.md` | Review checklist categories |
-| `project-memory/core-memory.md` | Feature history and prior decisions |
-| `.agent/workflows/build-feature-backend.workflow.md` | Implementation lifecycle phases |
-| `.agent/workflows/add-new-api-feature-module.md` | Module placement rules |
-
----
-
-## Step A — Implement
-
-1. **Read the module prompt file** (the path is given in your input).
-2. The prompt contains curated repo-map context and the full module specification. Follow it.
-3. **Implement.** The master plan was already user-approved. Proceed directly without stopping for approval.
-4. Follow `add-new-api-feature-module.md` for module placement and Do/Don't rules.
-
-## Step B — Test & Review (Auto-Approve)
-
-Run tests and quality review. **Auto-approve all internal decisions** — no human gates.
-
-1. **Run tests**
-   - Scope to the feature area if possible (e.g. `npm run test -- --testPathPattern=<feature-name>`).
-   - Otherwise run `npm run test`.
-   - Fix all failures before proceeding.
-
-2. **Code review** — invoke `/react-quality-review` skill
-   - The skill audits React components and patterns against quality standards.
-   - Auto-approve its findings and fix any required issues identified.
-   - No human intervention — this is part of the module's autonomous workflow.
-
-3. **Fix and re-verify**
-   - If review found issues or tests failed, implement fixes.
-   - Re-run tests. If fixes touched reviewed code, re-check via `/react-quality-review` again.
-   - Repeat until tests pass and all required findings are resolved.
-   - If a fix cannot be resolved after two attempts, exit with failure — the orchestrator will pause.
-
-## Step C — Commit & Push
-
-Once all tests pass and review is clean:
-
-1. **Create or update MODULE.md**
-   - In the feature module directory (`src/components/<feature-name>/MODULE.md` or similar), using `.agent/templates/MODULE.md`.
-
-2. **Update core-memory**
-   - Update `project-memory/core-memory.md` feature progress table:
-     - `<feature_name>: Module <N> completed (<brief description>); next: Module <N+1>.`
-
-3. **Commit the module**
-   - `git add .` (all changes from this module)
-   - `git commit -m "feat(MODULE_<N>): <brief description of what this module adds>"`
-   - Example: `git commit -m "feat(MODULE_2): Add PDF export dialog with queue management"`
-
-4. **Push to remote**
-   - `git push origin HEAD` (push to your current branch)
-   - If pushing to a protected branch, ensure your branch is up to date first
-
-5. **Update repo-map** (if module added new routes/components/services)
-   - Add/update the module entry in `project-memory/repo-map.md` (relevant sections).
-   - If a new reusable component, hook, or service was introduced, add it to the Reusable Components Registry.
-
----
-
-## Output
-
-When done, print a summary with:
-
-- What was implemented (key files created/modified)
-- Test results (pass/fail, coverage)
-- Review outcomes (findings, fixes applied)
-- Any remaining issues or deferred work
-
----
-
-## Do not
-
-- Implement more than one module. You handle exactly the module number given.
-- Skip Step B (verify). Always test, review, fix, and update docs.
-- Stop for human confirmation.
-- Create unnecessary files outside the scope of this module.