Skip to main content
Exécutez n'importe quel Skill dans Manus
en un clic
TonyWu20
Profil créateur GitHub

TonyWu20

Vue par dépôt de 25 skills collectés dans 6 dépôts GitHub.

skills collectés
25
dépôts
6
mis à jour
2026-05-19
explorateur de dépôts

Dépôts et skills représentatifs

compile-plan
Développeurs de logiciels

Compile fix/implementation plan documents into deterministic sd-based scripts that apply code changes without LLM interpretation. Use when the user says "/compile-plan <path>", "compile the plan", "generate scripts from the plan", or wants to turn a Before/After plan into executable scripts. Also use proactively after a plan-decomposer or review-pr produces a fix-plan.toml with Before/After blocks.

2026-04-23
enrich-phase-plan
Spécialistes en gestion de projets

Orchestrates a multi-agent pipeline to produce a detailed, reviewed, executor-ready TOML implementation plan from a high-level plan document. Use this skill when the user asks to "enrich the plan", "elaborate the next implementation plan", "prepare the TOML plan", "break down the plan into tasks", or wants to turn a high-level plan file into a concrete, executor-ready task breakdown. Run after /plan-review has approved the plan.

2026-04-23
fix
Développeurs de logiciels

Follow fix instructions from a specified document strictly, one task at a time. Use when the user says "/fix <document>", "follow the fix plan in <doc>", "execute fixes from <file>", or "apply the fixes in <document>".

2026-04-23
implementation-executor
Développeurs de logiciels

Strictly execute detailed implementation plans without modification or questioning. Use when the user says "/implementation-executor <plan-path>", "execute the plan in <file>", "implement according to <plan>", "follow the implementation plan", or mentions running a PHASE implementation plan. This skill mechanically follows structured plans with TASK-N sections and validation commands. ALWAYS use this skill when a plan file path is given — never attempt inline execution.

2026-04-23
next-phase-plan
Spécialistes en gestion de projets

Interactive skill for discussing and designing the next phase of a Fortran scientific project. Facilitates a conversation with the user about goals, scope, and high-level design, producing a markdown plan document as output. Use when the user says "/next-phase-plan", "plan the next phase", "what should the next phase do", "let's figure out the next steps", or wants to decide what the next phase should accomplish before breaking it into tasks. This is the FIRST step in the planning pipeline — its output feeds into /plan-review and then /enrich-phase-plan.

2026-04-23
plan-review
Développeurs de logiciels

Review a phase plan for architectural soundness before implementation begins. Reads the plan and any deferred improvements from prior phases, then asks the fortran-architect agent to validate the design, decide on deferred items, and surface architectural gaps. Use when the user says "/plan-review", "review the plan before implementing", or "check the plan first".

2026-04-23
review-pr
Analystes en assurance qualité des logiciels et testeurs

Review a branch's Fortran code against the project's plan, architecture, and style. Produces a PR rating and a detailed fix document for the author. Triggered by /review-pr [branch-name].

2026-04-23
define-outcomes
Spécialistes en gestion de projets

Interactive skill that helps users define desired outcomes for the next phase through Socratic grilling. Produces a PHASE_PLAN.md with concrete goals, scope boundaries, and success criteria. Uses grill-me + first-principle thinking to question priorities and foundations before committing to a plan. This is the recommended step before `/drive-outcomes`, especially when goals are still vague. Use when the user says "/define-outcomes", "define the outcomes", "clarify what we want", "what should the next phase achieve", "plan the next phase", or wants to decide what the next phase should accomplish before implementing.

2026-05-19
drive-outcomes
Développeurs de logiciels

Merged Stage 1+2 — define success criteria, explore against real fixtures, validate, implement, and produce a forensic record. One continuous session with a checkpoint in the middle. Use when the user says "/drive-outcomes <plan-path>", "drive the outcomes for this phase", after /define-outcomes completes, or when a phase plan is already ready for ODD-driven implementation.

2026-05-19
file-issue
Développeurs de logiciels

File a bug report or feature request for the odd-pipeline itself, with auto-gathered context from the current project and session. Use when the user says "/file-issue", "file a bug", "report an issue", "this is a pipeline problem", or encounters a pipeline defect during daily use.

2026-05-19
init-project
Développeurs de logiciels

Stage 0 — grill the user to settle the repo constitution: architecture, coding patterns, domain language, dependency choices, and tooling configuration. Produces CONTEXT.md (domain glossary + tooling config) and ADRs (architectural decisions). MUST be run before `/drive-outcomes` on any project. Use when the user says "/init-project", "set up the project constitution", "initialize the repo for the pipeline", or on a fresh project checkout before any planning begins.

2026-05-19
make-judgement
Analystes en assurance qualité des logiciels et testeurs

Review implemented changes against TASKS.md, produce review.md and fix-tasks.md for any defects found. Accepts a TASKS.md path and progressively loads group sections for validation. Use when the user says "/make-judgement <tasks-path>", "review the implementation", "judge the changes", or after /drive-outcomes completes for complex multi-group changes.

2026-05-19
debug-outcomes
Développeurs de logiciels

Debug an existing fixture-anchored system that passes its acceptance test but produces wrong output. Classifies prior investigation notes, establishes external anchor criteria, applies upstream-audit rule, implements fix with discriminator-value tests, and captures resolution. Use when the user says "/debug-outcomes", "debug this failure", "the test passes but the output is wrong", or describes a symptom in a system that already has fixture files and a passing (but loose) acceptance test.

2026-05-15
diagnose-tests
Analystes en assurance qualité des logiciels et testeurs

Scans a project's existing test suite for placebo test patterns (vacuous assertions, circular round-trip, unbounded thresholds, synthetic-only data). Produces a migration report to help projects adopt the Outcome-Driven Development (ODD) pipeline. Use when migrating from the old TDD pipeline, auditing test quality, or when the user says "/diagnose-tests", "audit my tests", "find placebo tests", or "how healthy are my tests?".

2026-05-15
drive-outcomes
Développeurs de logiciels

Merged Stage 1+2 — define success criteria, explore against real fixtures, validate, implement, and produce a forensic record. One continuous session with a checkpoint in the middle. Use when the user says "/drive-outcomes <plan-path>", "drive the outcomes for this phase", after /define-outcomes completes, or when a phase plan is already ready for ODD-driven implementation.

2026-05-15
define-outcomes
Spécialistes en gestion de projets

Interactive skill that helps users define desired outcomes for the next phase through Socratic grilling. Produces a PHASE_PLAN.md with concrete goals, scope boundaries, and success criteria. Uses grill-me + first-principle thinking to question priorities and foundations before committing to a plan. This is the recommended step before `/drive-outcomes`, especially when goals are still vague. Use when the user says "/define-outcomes", "define the outcomes", "clarify what we want", "what should the next phase achieve", "plan the next phase", or wants to decide what the next phase should accomplish before implementing.

2026-05-15
make-judgement
Analystes en assurance qualité des logiciels et testeurs

Review implemented changes against TASKS.md, produce review.md and fix-tasks.md for any defects found. Accepts a TASKS.md path and progressively loads group sections for validation. Use when the user says "/make-judgement <tasks-path>", "review the implementation", "judge the changes", or after /drive-outcomes completes for complex multi-group changes.

2026-05-15
debug-outcomes
Développeurs de logiciels

Debug an existing fixture-anchored system that passes its acceptance test but produces wrong physics or wrong output. Classifies prior investigation notes, establishes external anchor criteria, applies upstream-audit rule, implements fix with discriminator-value tests, and captures resolution. Use when the user says "/debug-outcomes", "debug this failure", "the test passes but the output is wrong", or describes a symptom in a system that already has fixture files and a passing (but loose) acceptance test.

2026-05-12
init-project
Spécialistes en gestion de projets

Stage 0 — grill the user to settle the repo constitution: architecture, coding patterns, domain language, dependency choices. Produces CONTEXT.md (domain glossary) and ADRs (architectural decisions). MUST be run before `/drive-outcomes` on any project. Use when the user says "/init-project", "set up the project constitution", "initialize the repo for the pipeline", or on a fresh project checkout before any planning begins.

2026-05-12
diagnose-tests
Analystes en assurance qualité des logiciels et testeurs

Scans a Rust project's existing test suite for placebo test patterns (vacuous assertions, circular round-trip, unbounded thresholds, synthetic-only data). Produces a migration report to help projects adopt the Outcome-Driven Development (ODD) pipeline. Use when migrating from the old TDD pipeline, auditing test quality, or when the user says "/diagnose-tests", "audit my tests", "find placebo tests", or "how healthy are my tests?".

2026-05-10
file-issue
Développeurs de logiciels

File a bug report or feature request for the rust-development-pipeline itself, with auto-gathered context from the current project and session. Use when the user says "/file-issue", "file a bug", "report an issue", "this is a pipeline problem", or encounters a pipeline defect during daily use.

2026-04-29
6 dépôts affichés sur 6
Tous les dépôts sont affichés