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

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

Commencer

workflow-plan-output

Étoiles15

Forks2

Mis à jour20 juin 2026 à 10:05

Expected shape of the planning phase output before code-implementer; aligns with write-implementation-plan.

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

meta-secret

meta-secret/meta-secret-core

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

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	workflow-plan-output
description	Expected shape of the planning phase output before code-implementer; aligns with write-implementation-plan.

Workflow — plan output

The feature-planner subagent owns the planning phase. Plans must be architecture-safe and file-oriented.

Read first

CLAUDE.md
ARCHITECTURE.md
../write-implementation-plan/plan-template.md
Optional deeper plan: ../write-implementation-plan/SKILL.md

Output checklist

Goal and non-goals
Crates and files touched (paths under meta-secret/)
Ordered steps
Risks
Verification commands: task … from repo root for Docker/CI parity (see .ai/skills/build-via-task/SKILL.md); narrow cargo from meta-secret/ when appropriate
Explicit wait for user approval before implementation

Do not duplicate full templates here—use write-implementation-plan/plan-template.md for the question list.

Plus depuis ce dépôt

même dépôt

workflow-mr-body

meta-secret/meta-secret-core

Draft and update PR/MR title and description from full branch scope; use before gh pr create or gh pr edit.

2026-06-2015

meta-skill

meta-secret/meta-secret-core

Write or update project skills and rules markdown files (.ai/skills/, .ai/rules/, .cursor/rules/). Use when creating a new SKILL.md or rule, updating an existing one, or when the user asks to document a workflow, pattern, or convention as a reusable skill.

2026-06-1815

core-guardian

meta-secret/meta-secret-core

Guard architecture, style, and security in meta-secret core crate changes.

2026-04-2715

cli-guardian

meta-secret/meta-secret-core

Guard architecture, style, and security in cli/meta-cli changes.

2026-04-2215

mobile-lib-guardian

meta-secret/meta-secret-core

Guard architecture, style, and security in mobile/uniffi library changes.

2026-04-2215

web-guardian

meta-secret/meta-secret-core

Guard architecture, style, and security in web-cli/ui changes.

2026-04-2215

name	workflow-plan-output
description	Expected shape of the planning phase output before code-implementer; aligns with write-implementation-plan.

Workflow — plan output

The feature-planner subagent owns the planning phase. Plans must be architecture-safe and file-oriented.

Read first

CLAUDE.md
ARCHITECTURE.md
../write-implementation-plan/plan-template.md
Optional deeper plan: ../write-implementation-plan/SKILL.md

Output checklist

Goal and non-goals
Crates and files touched (paths under meta-secret/)
Ordered steps
Risks
Verification commands: task … from repo root for Docker/CI parity (see .ai/skills/build-via-task/SKILL.md); narrow cargo from meta-secret/ when appropriate
Explicit wait for user approval before implementation

Do not duplicate full templates here—use write-implementation-plan/plan-template.md for the question list.