Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

02-challenge

Estrelas29

Forks2

Atualizado11 de junho de 2026 às 06:19

Rethink prior work to verify correctness against an agreed plan, classifying findings as deal-breakers, suggestions, or correct, with a confidence score. Use when the user says "challenge this", "rethink your plan", "is this correct", "review my last decision", "challenge my decision", "challenge what you did", "is my decision right", "criticize this", "find flaws", or asks for a critical review of just-completed work. Do NOT use for line-by-line code review against a style guide, implementing features, writing tests, or generating new code.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

ai-driven-dev

ai-driven-dev/aidd-framework

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Especialistas em gestão de projetosNegócios e Operações Financeiras·SOC 13-1082

Explorador de arquivos

4 arquivos

SKILL.md

readonly

Mais deste repositório

mesmo repositório

00-onboard

ai-driven-dev/aidd-framework

Detect the current project's state and open a hub of project actions - understand the project, set up or refresh the memory bank, or continue the AIDD development journey. Silently inspects the project, the AIDD setup, and which AIDD plugins are installed, then adapts the menu to that context. Use when the user says "where do I start", "onboard me", "onboard me to this project", "what should I run next", "what should I work on next", "what's the state of this project", "guide me through aidd", "guide me through aidd-context", or invokes `aidd-context:00-onboard`. Do NOT use to enumerate every installed surface from raw user intent (the discovery skill in this plugin handles that).

2026-06-1129

01-bootstrap

ai-driven-dev/aidd-framework

Imagine and validate the technical architecture of a new SaaS through interactive Q&A, candidate-stack comparison, multi-agent audit, and an INSTALL.md output. Use when starting a new SaaS project, choosing a stack, designing the architecture pattern (monolith vs microservices vs serverless), or producing a project's INSTALL.md. Do NOT use for editing an existing project's stack, database schema design, or scaffolding actual files (this skill produces docs only, no code).

2026-06-1129

02-project-init

ai-driven-dev/aidd-framework

Initialize or refresh the project memory bank and ensure AI context files contain the project memory block. Use when running `aidd init` for the first time, bootstrapping a new project, or re-running the init flow on an existing project. Do NOT use for updating individual memory files after they exist - use `aidd-context:05-learn` instead; do NOT use for editing a single rule - edit the file directly.

2026-06-1129

03-context-generate

ai-driven-dev/aidd-framework

Generate context artifacts (skills, agents, rules, commands, hooks, plugins, marketplaces) across the host AI tool(s) the project uses. Use when the user wants to create, refactor, add or remove actions in a skill, migrate a legacy slash command into a router-based skill, or generate a new agent, rule, command, hook, plugin, or marketplace. Do NOT use for editing a single action inside an existing skill (edit directly), writing MCP servers, or modifying project-level files.

2026-06-1129

04-mermaid

ai-driven-dev/aidd-framework

Generate high-quality Mermaid diagrams from markdown content using a structured plan-validate workflow.

2026-06-1129

05-learn

ai-driven-dev/aidd-framework

Capture and store project-level learnings, conventions, and decisions surfaced during work into memory, decisions, or rules. Use proactively when the user states a durable project rule or convention ("for next", "always do X", "from now on", "going forward", "rule:", "convention:"), records a technical decision and its rationale, deprecates something, or notes an insight that should outlive the current task. Do NOT use for personal or AI-preference reminders (those belong to user memory), routine code edits, minor fixes, or anything already captured.

2026-06-1129

name

02-challenge

description

Challenge

Rethink prior work and surface what is wrong, missing, or duplicated. Output a structured report with a confidence score so the user knows whether to ship, iterate, or rework.

Available actions

#	Action	Role	Input
01	`challenge`	Rethink prior work, classify findings, score confidence	review_target + agreed_plan

Default flow

Single action skill. The router dispatches to challenge whenever the trigger phrases above appear.

Transversal rules

Think in first principles. Every step must be logical, with no gap and no missing information.
Challenge own assumptions and the user's decisions before declaring confidence.
Look for edge cases, errors, inconsistencies, missing parts, duplications, and optimizations.
Aim for simplifications. If the work can be smaller, say so.
Output the structured report verbatim per the action's ## Outputs block.

References

@references/confidence-rubric.md: tiered rubric for the confidence percentage.

Assets

None.

External data

None.