palarran-product-acquisition

Topics in the source

• Product acquisition
• Mandatory foundation — before research
• Target and boundaries
• Domain work
• Verification, decisions and handoff
• Explicit runtime pipeline
• First buyers before MVP

Shared cycle: before work and after checks follow global memory: bounded recall → applicability → sanitized verified learn/dedup. This memory scope is explicitly authorized; other profile restrictions remain. --plan permits no network/publication; outages do not block the main task. Invoke /palarran:product:acquisition {description/object} or $palarran-product-acquisition. Work only on this skill's question; never start other product stages automatically. Read map, evidence contract, workflow and memory, data/API access, primary sources, case map, domain cases, domain guide and output template. Missing mandatory docs: report the blocker/request checkout path rather than substituting general knowledge. Explain the case used, why it applies and what not to transfer. Resolve the current SKILL.md symlink and identify installed checkout separately from target project. Read shared memory, target .palarran/INDEX.md, product catalog/accepted ADRs/revisions/handoffs and README. Without a description use actual project context; unclear business/key geography requires one specific question while continuing independent work. Never override the user's chosen product/alternatives. Scope: read-on

This is an excerpt. Refer to the complete source and its current requirements.