Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

flow

Étoiles1

Forks0

Mis à jour3 juin 2026 à 11:28

Use when the user wants logic validation: states, transitions, invariants, edge cases, dead ends, and blockers before implementation.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

JustineDevs

JustineDevs/meta-architect

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

name	flow
description	Use when the user wants logic validation: states, transitions, invariants, edge cases, dead ends, and blockers before implementation.

Flow

Use this skill inside Codex to pressure-test how the system behaves, not just how it is structured.

Output

Produce:

decision, status, evidence, blockers, next_allowed_triggers
key actors and system states
state map and failure flows
main flows and failure flows
invariants and state transitions
race conditions, dead ends, and consistency risks
missing requirements or ambiguous behavior
exact next trigger, usually $vet

Rules

Focus on behavior, not UI polish or low-level code details.
Surface ambiguity aggressively when it affects correctness.
Prefer simple state models over sprawling branching logic.

Plus depuis ce dépôt

même dépôt

arch

JustineDevs/meta-architect

Use when the user wants architecture-first product and system design with explicit stack rationale, boundaries, tradeoffs, data model choices, and phased delivery planning.

2026-06-031

build

JustineDevs/meta-architect

Use when the user wants to decide whether implementation is ready, what remains blocked, and what the exact next build step should be.

2026-06-031

sage

JustineDevs/meta-architect

Use when the user wants evidence-backed technology choices, OSS evaluation, and source-grounded validation of the stack proposed in `$arch`.

2026-06-031

vet

JustineDevs/meta-architect

Use when the user wants a security and trust-boundary review of the current design before implementation or release.

2026-06-031

vibe

JustineDevs/meta-architect

Use when the user wants a DX and UX review of the planned workflow before implementation proceeds.

2026-06-031

align

JustineDevs/meta-architect

Use when the user needs scope alignment, shared language, or docs clarity before or between gated lanes.

2026-05-181

name	flow
description	Use when the user wants logic validation: states, transitions, invariants, edge cases, dead ends, and blockers before implementation.

Flow

Use this skill inside Codex to pressure-test how the system behaves, not just how it is structured.

Output

Produce:

decision, status, evidence, blockers, next_allowed_triggers
key actors and system states
state map and failure flows
main flows and failure flows
invariants and state transitions
race conditions, dead ends, and consistency risks
missing requirements or ambiguous behavior
exact next trigger, usually $vet

Rules

Focus on behavior, not UI polish or low-level code details.
Surface ambiguity aggressively when it affects correctness.
Prefer simple state models over sprawling branching logic.