「re-entry」の検索結果

Use on any core for first-run planning intake — Phase 0 runs the vendored BMAD-METHOD planning shelf, shared by every core, and Phase 1 (mining `04-prd.md` into intent records plus the Add-ons/sync-and-remote-entities decision) is full-stack-app's and pwa-app's shared procedure — identical mechanics, a different decision at step 5/8. Phase 0 also defines compressed intake, the path a user's explicit "just build it" choice takes on full-stack-app, pwa-app, authored, and copywriting cores: one batched round of questions in place of the shelf, writing a thinned archive at the same paths so Phase 1 (or, on copywriting, that core's own mining step), `ux-planner`, and the Re-entry pass all keep their documented source. Also use for the Re-entry pass, which mines new scope into additional intents without re-running the shelf, on any core with a module axis to add an intent to (full-stack-app, pwa-app, authored) — landing-page has none, so its own new-scope path runs through `hedgehog-landing-loop`'s Correction Protocol instead. Invoked by the `planner` agent, which decides the path; don't run standalone. landing-page runs this skill's Phase 0 on first run, then mines the same archive through `hedgehog-landing-loop`'s own planning-intake section, that core's counterpart to this skill's Phase 1. copywriting runs this skill's Phase 0 the same way (full or compressed), then mines the same archive through `hedgehog-copywriting-loop`'s own planning-intake section into a what/audience/register brief — no module axis, so its own new-scope path runs through that loop's Correction Protocol rather than the Re-entry pass below. An authored core runs this skill's Phase 0, then `hedgehog-core-design`, then this skill's Phase 1 mining against the designed layer sequence. A brownfield adoption (`hedgehog-adopt`) never runs this skill's shelf at all — the drivers BMAD elicits are already settled facts of a repo that already exists.

日本語の概要は準備中です。原文の説明を表示しています。

Expert-level astrodynamics covering orbit determination, trajectory optimization, launch vehicle ascent, re-entry dynamics, and numerical methods for space mission analysis.

日本語の概要は準備中です。原文の説明を表示しています。

Detects Follow-Through Day (FTD) signals for market bottom confirmation using William O'Neil's methodology. Dual-index tracking (S&P 500 + NASDAQ) with state machine for rally attempt, FTD qualification, and post-FTD health monitoring. Use when user asks about market bottom signals, follow-through days, rally attempts, re-entry timing after corrections, or whether it's safe to increase equity exposure. Complementary to market-top-detector (defensive) - this skill is offensive (bottom confirmation).

日本語の概要は準備中です。原文の説明を表示しています。

Wash sale detection under 2025 US crypto rules with 61-day window monitoring, disallowed loss tracking, and safe re-entry countdown

日本語の概要は準備中です。原文の説明を表示しています。

Maps your company's GTM motion (PLG, SLG, or Hybrid) to concrete funnel stages with inputs, outputs, and qualification criteria per stage. Detects motion type from website + Exa research, then produces pre-close + post-close stage definitions, the FETE mapping (Fit / Engagement / Tier / Eligibility), and closed-lost re-entry paths. Triggers - "funnel strategy", "funnel stages", "pipeline stages", "sales process", "lead qualification", "GTM motion mapping", or any work defining how leads flow through the business. Upstream - recommended company-context, icp-research. Downstream - feeds lifecycle-marketing, outreach-emails, content-strategy. NOT for lead scoring logic (use /lead-scoring) or lifecycle email campaigns (use /lifecycle-marketing).

日本語の概要は準備中です。原文の説明を表示しています。

Record findings from completed offline human tasks (interviews, observations, outreach) back into the canvas. The re-entry point after /mycelium:handoff.

日本語の概要は準備中です。原文の説明を表示しています。

Observe and assess a garden using a structured sensory protocol adapted from Coordinate Remote Viewing. Covers pre-entry clearing (meditate checkpoint), Stage I gestalt impression, Stage II sensory layer (leaf, stem, root, soil), Stage III pattern recognition with AOL management, and garden health triage matrix (heal checkpoint). Use before any intervention, when plants show stress symptoms, at seasonal transitions, when evaluating a new garden site, during regular health monitoring, or after extreme weather events such as frost or heat waves.

日本語の概要は準備中です。原文の説明を表示しています。

Builds and audits a concept-ontology for a regelrecht corpus to decide and verify reference types — cross-law source-binding vs intra-law source-binding vs open-norm leaf vs external-fact leaf — and to catch concept conflation across laws. Core principle: a value's reference type is fixed by WHO derives it, and a binding is sound only when producer and consumer denote the SAME concept; the lexical surface (the word in the text) is not the concept. Detects false friends (one term, different concepts — e.g. a register-based vs a factual "naar de omstandigheden"-based residence/ingezetene concept), orphan plain-params (a value a regulation actually derives, modeled as a brute input), negation/complement re-entry (¬X modeled as an independent leaf next to X), and duplication (one concept re-entered as several independent leafs, losing the single-source-of-truth invariant). Produces a law-level glossary and a stelsel-level concept map with sound same-concept binding edges and flagged lexical-match-but-concept-mismatch edges. Use when deciding whether a value should be cross-law/intra-law/leaf, when the same term means different things across laws, or when a binding might silently conflate concepts.

日本語の概要は準備中です。原文の説明を表示しています。

Use when setting up, configuring, or troubleshooting Marketing Cloud Journey Builder — including entry sources, activities, decision splits, wait activities, goals, exit criteria, journey versions, test mode, or journey analytics. Triggers: 'journey builder setup', 'entry source configuration', 'decision split not routing', 'exit criteria not removing contacts', 'goal not tracking conversion', 'journey version publishing', 'journey re-entry settings', 'wait activity date field'. NOT for coding a custom activity or entry source — use apex/marketing-cloud-custom-activities. NOT for business units and sender profiles — use admin/marketing-cloud-engagement-setup.

日本語の概要は準備中です。原文の説明を表示しています。

Coordinate a requested unattended sprint with two explicitly selected desktop control surfaces and independent gated review. Requires proven re-entry on both and a current-run human opt-in.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a driver has been involved in a crash — regardless of preventability or injury — and the carrier needs to handle the immediate, post-investigation, and return-to-work phases. Covers trauma response, post-accident testing under 49 CFR 382.303, paid time off, retraining, light duty, and re-entry planning.

日本語の概要は準備中です。原文の説明を表示しています。