| name | pattern-shishen |
| description | ???????????Use when ???? or ???? has identified ?? as a pattern candidate and Codex must evaluate formation supports,?? risks,?? possibilities, and product-facing interpretation without deterministic fate claims. |
?????
Source
When to Use
Use when upstream skills have produced a ??? candidate:
yueling-quge establishes the month-command entry.
yongshen-bianhua confirms no stronger pattern change overrides it.
- This skill evaluates the specific ??? conditions.
Inputs
{
"pattern_candidate": "???",
"day_master": "",
"month_branch": "",
"revealed_stems": [],
"hidden_stems": {},
"ten_gods": {},
"combinations_clashes": [],
"roots_strength": {}
}
Procedure
- Confirm that ?? is genuinely active as a pattern force, not merely present.
- Check formation supports: ?????????.
- Check?? risks: ?????????.
- Send mixed cases to
yongshen-chunza and yongshen-chengbai-jiuying.
- If a key supporting condition is required, call
xiangshen-shibie.
- Produce product language around: ?????????????.
Output
{
"pattern": "???",
"candidate_strength": "?|?|?|??",
"formation_supports": [],
"failure_risks": [],
"rescue_candidates": [],
"needs_next_skill": [],
"plain_explanation": "",
"product_keywords": ["?????????????"]
}
Boundaries
- Do not make deterministic fate claims.
- Do not equate the pattern name with a real-world profession or fixed outcome.
- Do not skip upstream ???? and ????.
- Do not ignore?? and??.