One-click install
npx skills add https://github.com/BlocUnited-LLC/mozaiks --skill existing-app-discovery-change
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: existing-app-discovery-change
Source: https://github.com/BlocUnited-LLC/mozaiks/tree/main/.claude/skills/existing-app-discovery-change
Command: npx skills add https://github.com/BlocUnited-LLC/mozaiks --skill existing-app-discovery-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you review and implement changes to Mozaiks’ brownfield or existing-app discovery flow without breaking routing, contracts, or adoption classification.

Core Features & Use Cases

  • Brownfield Discovery Guardrails: Keeps ExistingAppDiscovery scoped to brownfield/adoption evidence generation, not greenfield build or code-copy migrations.
  • Preload Scanning & Detection Updates: Guides deterministic updates to preload discovery context variables, storage/connector/auth/security detection, and adoption classification inputs.
  • Artifact Saving & Contract Alignment: Ensures saved discovery artifacts and downstream handoffs remain compatible with workflow-local contracts and the canonical AppContextVersion direction.
  • Testing & Impact Awareness: Calls out the most relevant routing/discovery contract tests to run based on what you changed (preload vs routing vs artifact contracts).

Quick Start

Use this skill to review a proposed change to ExistingAppDiscovery by asking it to identify the affected brownfield workflow surfaces, classifiers, detectors, artifacts, and the exact tests to run based on the changed files you provide.

Frequently Asked Questions about existing-app-discovery-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely modify existing app discovery workflows without breaking brownfield adoption routing?

Brownfield modernization requires keeping ExistingAppDiscovery scoped strictly to adoption evidence generation, ensuring preload scanning updates and artifact handoffs remain compatible with downstream consumption contracts and canonical AppContextVersion structures.

How do I validate contract changes for preload scanning and artifact handoffs in existing app discovery?

You validate changes by providing the modified files to identify affected brownfield workflow surfaces, classifiers, and detectors, which determines the exact session routing and discovery contract tests you must run.

Does brownfield app adoption support gradual modernization and module decomposition outputs?

Yes, gradual modernization and module decomposition outputs are supported as adoption evidence types, but the workflow strictly separates this evidence from canonical AppContextVersion to preserve routing integrity.

What tests should I run when changing preload discovery context variables or storage connectors?

You should run session routing, launcher, and discovery contract suites specifically aligned to the impacted preload scanning, classification, or artifact contract surfaces you modified.

When should I not use existing app discovery tooling for application modernization?

You should avoid using existing app discovery tooling for greenfield builds or code-copy migrations, as the guardrails are designed exclusively to validate brownfield adoption evidence and workflow routing.