brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
adobe-multi-env-setupSeparate Adobe development, stage, and production organizations/projects/workspaces, credentials, profiles, storage, events, budgets, and evidence. Use when the task requires adobe multi-environment isolation. Trigger with "Adobe environments", "separate Adobe staging", or "Adobe workspace setup".
Independent GitHub snapshot · Automated classification · Original documentation governs
Separate Adobe development, stage, and production organizations/projects/workspaces, credentials, profiles, storage, events, budgets, and evidence. This workflow produces a reviewable artifact and evidence before any live side effect.
App Builder provides isolated workspaces such as Stage and Production within a project, while some risk boundaries require separate projects or credentials. Environment equivalence must be proven from configuration and entitlement, not assumed from names. Recheck the dated evidence map before relying on mutable product behavior.
Each credential is bound to one declared environment and secret store. Product profiles, redirect URIs, event registrations, storage buckets, and consenting users are independently mapped.
Use Read, Glob, and Grep to inspect current documentation, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Skill invocation alone does not authorize network access, credentials, Adobe content, consent, uploads, generation, spend, deployment, registration changes, replay, cancellation, or deletion.
Security and organization admins approve environment/credential/profile creation; data and budget owners approve storage and live workloads; teardown and deletion require separate approval.
Return the environment matrix, isolation rationale, typed manifest, parity results, promotion gate, drift controls, and owners. Mark assumptions, observed environment behavior, owners, evidence dates, and unresolved gaps explicitly.
Exercise and record expected and observed results for: