القائمة
Compatibility research entrypoint for advanced coding models. Use only when the operator invokes the older research name for the canonical pre-plan deep-research workflow.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Advanced post-Review human acceptance workflow. Use after fresh approved Review closeout to restore a contextless human's understanding, guide one real product step at a time, and persist an explicit pass, fail, or blocked verdict.
Read-only cross-artifact consistency analysis for advanced coding models. Use when tasks exist and the specification, plan, and task boundaries need an independent gate before or during execution.
Existing-spec repair workflow for advanced coding models. Use when a specification package has planning-critical ambiguity, weak acceptance, contradictions, or new constraints that should be absorbed without recreating the feature.
Focused pre-plan feasibility research for advanced coding models. Use when a planning-ready specification still lacks a credible implementation chain, external evidence, or a disposable proof.
Lean design-system workflow for advanced coding models. Use for a new product UI, redesign, rebrand, shared visual language, or an audit/update of the root DESIGN.md contract.
Resumable product and technical discussion for advanced coding models. Use when a rough idea needs durable decisions and options before formal specification.
| name | spx-research |
| description | Compatibility research entrypoint for advanced coding models. Use only when the operator invokes the older research name for the canonical pre-plan deep-research workflow. |
Read references/project-learning.md and apply its consume-capture policy using command deep-research.
Read references/project-cognition.md only to preserve the shared evidence
boundary; defer cognition intake to $spx-deep-research. This is a
compatibility route, not a separate artifact lifecycle.
If the request is generic web research rather than feasibility work for a planning-ready feature specification, route it to the installed external/web research skill and do not create feature artifacts.
Preserve the complete request and continue immediately with
$spx-deep-research. Do not create spx-research state, duplicate evidence,
or emit a second report. The canonical workflow owns deep-research.md,
optional research-spikes/, workflow state, and the planning handoff.
This invocation authorizes only the deep-research compatibility route. After
$spx-deep-research returns, stop and report its handoff; do not continue to
$spx-plan.
