Menu
Review whether SoulMap AI is ready to ship by checking docs, changelog, tests, packaging, and user-facing claims for release consistency.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | release-readiness-review |
| description | Review whether SoulMap AI is ready to ship by checking docs, changelog, tests, packaging, and user-facing claims for release consistency. |
| disable-model-invocation | true |
Use this skill before shipping notable changes to the repository.
This skill is for launch and release hygiene, not feature ideation.
ai-prompt-engineering-safety-review
or operations-and-safety-reviewresearch-and-gap-analysisdocs-and-api-writerCheck whether the repo tells a consistent, shippable story across:
Always inspect:
README.mdCHANGELOG.mddocs/engineering/DEV.mddocs/engineering/TESTER.mddocs/engineering/API.mddocs/operations/OPERATIONS.mdtemplates/launch-readiness-checklist.mdtests/Verify that newly added modules, workflows, or constraints are reflected in docs.
Verify that CHANGELOG.md captures meaningful added, changed, or removed behavior.
Check whether important changes are protected by:
Confirm that the distribution artifact still matches what the repo claims to ship.
Check whether README and public-facing docs make claims the implementation can support.
When reviewing, structure the result as:
List shipping blockers or inconsistencies first.
Summarize what was updated to restore readiness.
Call out anything still unverified, untested, or intentionally deferred.
The repo should be:
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.