Results for “partial-success”

当需要在多个领域积累独特竞争优势，避免单一技能风险时

Use this skill to evaluate which DataQ challenges have winning evidence and which don't. Covers documented vs anecdotal evidence and the 8 high-success patterns.

当遭遇挫折、失败或结果不如预期时，用于将负面经验转化为成长燃料

Graceful degradation when primary approach fails. Try alternates in priority order; record which path succeeded for future routing.

>-

Sentinel Validation & Project Promotion

Create product objectives, key results, initiatives, guardrails, and review cadence.

Performance-coaching mode for repeated failures, passive behavior, completion-quality issues, or explicit try-harder requests. Uses structured troubleshooting and evidence-first delivery habits.

Reviews closed trades, partial exits, and monthly trade aggregates for process adherence, risk discipline, execution quality, and evidence-based trading behavior patterns.

Imported skill _template from vercel

Autonomously repairs failed task verification by choosing retry, decompose, prune, or escalate strategies before surfacing to the user.

Execute the next incomplete step (or full phase with --phase), ship the result, and prepare the next step

Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"

Skeptical pushback on visual placement — both density and quality. Reads the annotated outline plus the visuals manifest and asks (a) whether the article hits the density target from editorial-principles-visuals.md, (b) whether each [VISUAL:...] earns its place, (c) whether sections without one would benefit. One revision pass on FAIL (BLOG_AGENT_VISUALS_REVISION_BUDGET, default 1).

Fix failing or flaky Playwright tests. Use when user says "fix test", "flaky test", "test failing", "debug test", "test broken", "test passes sometimes", or "intermittent failure".

Facilitate a structured sprint retrospective to surface insights and produce actionable improvements with owners and deadlines.

v4.1.0 reward function redesign to fix overtrading and DSR dominance

Performance-coaching mode for repeated failures, passive behavior, completion-quality issues, or explicit try-harder requests. Uses structured troubleshooting and evidence-first delivery habits.

Towards Open-World Segmentation of Parts

在启动高风险项目或重要决策前，需要预先识别潜在失败点以增强心理韧性和方案鲁棒性时

Guides the red-green-refactor cycle for implementing features with test-driven development, including test quality guidelines, framework setup, and commit patterns.

Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.

Copy-Paste Augmentation for Instance Segmentation

Fix failing or flaky Playwright tests. Use when user says "fix test", "flaky test", "test failing", "debug test", "test broken", "test passes sometimes", or "intermittent failure".

Structured workflow to reproduce, diagnose, plan, fix, verify, and record a bug fix, requiring a deterministic reproduction before diagnosis and minimal changes only.

Conduct failure mode and effects analyses. TRIGGERS - Use when user needs help with fmea-guide related tasks.