القائمة
Design repeatable development and release workflows for SoulMap AI so recurring tasks become structured, automatable, and easier to hand off.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
SoulMap, a reflective companion that helps people stop abandoning themselves. Includes a central coordination layer, a clear response pipeline, routing guidance, depth calibration, epistemic guardrails, safety guardrails, voice system, brand doctrine, and reusable templates. Mirror, not guide.
Build and maintain Python detector modules that identify framework selection signals in conversation history.
SoulMap reflective response frameworks covering emotional de-escalation, grief, existential reflection, inner parts, life direction, shadow work, synthesis, and relational inquiry. Relevant for tasks that require choosing or applying the core reflective method for a user conversation.
SoulMap safety and boundary rules covering crisis handling, dependency prevention, trauma-informed language, prompt injection defense, and scope control. Relevant for requests that involve harm, escalation, refusal, redirection, or questions about what SoulMap must not do.
SoulMap symbolic spiritual materials covering brand-safe numerology, chakra policy, healing metaphors, and archetypal language. Relevant for tasks that involve spiritual framing within SoulMap's grounded, non-predictive, non-grandiose boundaries.
SoulMap brand doctrine, positioning, message hierarchy, surface-specific rules, and strategic direction. Relevant for tasks that concern what SoulMap is, what it is not, how it sounds in public, or how brand language stays aligned across product surfaces.
| name | workflow-automation-designer |
| description | Design repeatable development and release workflows for SoulMap AI so recurring tasks become structured, automatable, and easier to hand off. |
| disable-model-invocation | true |
Use this skill when turning a repeated manual process into a documented workflow, automation plan, or CI-friendly sequence.
Examples:
Before designing any workflow, inspect the relevant existing tooling and contracts:
../rules/repo-workflow.md, current working discipline and quality checks.github/workflows/, existing CI workflowssrc/soulmap/devtools/, canonical Python tooling packagescripts/, bash helper scriptsdocs/engineering/DEV.md, developer setup and day-to-day commandsdocs/operations/OPERATIONS.md, operational checklists and release guidancetemplates/launch-readiness-checklist.md, release gate templaterelease-readiness-reviewresearch-and-gap-analysisdocs-and-api-writerConvert repeated repo work into clear, reproducible steps.
Identify tasks that happen often and currently rely on memory.
Make sure the order of steps is correct and safe.
Choose the simplest workflow that fits the repo's current tooling.
Ensure another contributor can run the workflow without hidden context.
Summarize the manual flow today.
List the improved step-by-step sequence.
Call out which parts fit scripts, CI, or checklists.
The workflow should be: