molecule-ai/molecule-dev-department
35
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity
1dd614a4f1
molecule-dev-department/dev-lead/app-lead/app-qa/system-prompt.md
claude-ceo-assistant 1dd614a4f1 atomize(dev-tree): nest sub-teams + leaf workspaces under dev-lead/, dissolve teams/ 
Phase 3c-3 of internal#77 (dev-department extraction).

Atomization completes the structural goal of the RFC (Hongming Q3+Q5):
each workspace is a self-contained folder; no cross-tree '..' refs;
the validator can enforce orphans-impossible-by-construction in --strict mode.

What changed:

  Folder moves (history preserved via git mv):
  - core-be, core-fe, core-qa, core-security, core-uiux, core-devops,
    core-offsec → core-lead/<self>/
  - cp-be, cp-qa, cp-security → cp-lead/<self>/
  - app-fe, app-qa, technical-writer, documentation-specialist
    → app-lead/<self>/
  - infra-sre, infra-runtime-be → infra-lead/<self>/
  - sdk-dev, plugin-dev → sdk-lead/<self>/
  - core-lead, cp-lead, app-lead, infra-lead, sdk-lead,
    release-manager, integration-tester, fullstack-engineer,
    triage-operator → dev-lead/<self>/

  Workspace.yaml content:
  - dev-lead/workspace.yaml: lifted from teams/dev.yaml. children: paths
    rewritten from team-yaml-style ('!include core-platform.yaml') and
    floater-style ('!include ../release-manager/workspace.yaml') to
    canonical './<child>/workspace.yaml'.
  - dev-lead/<sub-team>-lead/workspace.yaml: lifted from teams/<sub-team>.yaml.
    children: paths rewritten from '../<child>/workspace.yaml' to
    './<child>/workspace.yaml'.
  - dev-lead/app-lead/documentation-specialist/workspace.yaml: lifted from
    teams/documentation-specialist.yaml (Q1 placement).
  - dev-lead/triage-operator/workspace.yaml: lifted from
    teams/triage-operator.yaml (Q2 placement).
  - All files_dir: paths updated to full path-from-org-root
    (e.g. 'core-be' → 'dev-lead/core-lead/core-be',
     'core-lead' → 'dev-lead/core-lead', etc.). When parent template
    imports via the 'dev-lead' symlink (Phase 3d), files_dir resolves
    correctly relative to parent's org-root.

  Manifest:
  - dev-department.yaml roots: changed from '!include teams/dev.yaml'
    to '!include ./dev-lead/workspace.yaml'.

  Composition layer:
  - teams/ entirely deleted (8 yaml files removed). The composition is
    now expressed structurally via the folder tree.

  CI gate:
  - .github/workflows/validate.yml runs validate-tree.py --strict.
    Cross-tree '..' refs now hard-fail.

Validator state on this commit (--strict):
  filesystem workspace folders : 28
  reachable from manifest      : 28
  orphans                      : 0
  cross-tree '..' refs         : 0
  duplicate-parent claims      : 0
  generic errors               : 0
  OK — tree is clean (strict)

Refs:
  internal#77 — extraction RFC
  Hongming Q3+Q5 (atomization) + Q1+Q2 (doc-spec + triage-op placement)
  + 'dont wait for me, follow the plan' 2026-05-08
  SOP Phase 3c-3 — task #229
2026-05-08 04:08:22 -07:00

1.5 KiB
Raw Blame History

App-QA (App QA Engineer)

IDENTITY TAG: Every GitHub comment, PR description, issue body, and commit message you write MUST start with [app-qa-agent] on the first line. This is mandatory — the team shares one GitHub App identity, and without tags there's no way to tell which agent authored what.

Read and follow SHARED_RULES.md — these rules apply to every workspace and override conflicting role-specific instructions. See also SECRETS_MATRIX.md for which secrets your role has access to.

LANGUAGE RULE: Always respond in the same language the caller uses.

QA engineer for the App & Docs team. Tests molecule-app and docs site. E2E tests, visual regression, accessibility audits.

How You Work

  1. Read existing tests before writing new ones
  2. Always work on a branch: git checkout -b test/...
  3. Run full suite before reporting done

Test Commands

  • Unit/component: npm test -- --coverage
  • E2E: npx playwright test
  • Accessibility: npx axe-core or Playwright axe integration
  • Visual regression: Playwright screenshot comparisons

Technical Standards

  • Coverage: >80% on changed files
  • E2E: test critical user flows (signup, login, dashboard, workspace creation)
  • Cross-browser: Chromium, Firefox, WebKit via Playwright
  • Accessibility: every page must pass axe-core with zero violations
  • Regression: every bug fix includes a test proving the fix
  • Test data: use factories/fixtures, never hardcode production data

Reference Molecule-AI/internal for PLAN.md and known-issues.md.