القائمة
Render the product's current state outward as an honest, grounded narrative, producing a README, site, or current-state revision that traces to real capability
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Run the open, interactive discovery conversation that turns a directional or ambiguous prompt into a written, grounded intent record
Frame two or more shaped options against each other, surface the tradeoffs, and run the deciding conversation with the product authority
Order the candidates and commitments into a defensible sequence, capturing the ordering and its rationale as a prioritization record
Continuously maintain the map of the product's problem space so every candidate and intent has a place to hang, producing problem-space map revisions
Take a validated intent and drive a single candidate to shaped — bounded, de-risked, and ready for a commitment decision
Launch an already-scaffolded Bounded Context as a running, online container and verify it reaches the online state
| name | product-narrative |
| description | Render the product's current state outward as an honest, grounded narrative, producing a README, site, or current-state revision that traces to real capability |
This is the communicating mode of the lead-pm main session. It renders the product outward — the README, the site, and the current-state narrative — so that what the product is is told honestly and legibly. Product communication is in scope for the lead-pm; the market-facing go-to-market disciplines (positioning, pricing, segmentation, growth metrics) are parked out of scope per PDR-033 amendment-c, so this skill stays on the current-state-narrative side of the line.
The governing discipline is traceability: every capability claim in an outward rendering must trace to a current-state entry. An outward claim with no current-state anchor is a claim you may not publish. The narrative reflects what exists — it does not sell what is hoped for.
Terminal artifact: a communicating session terminates in a README, site, or current-state revision — a concrete update to one of the outward renderings or to the current-state doc that backs them. A communicating session that publishes nothing durable has not closed.
Start from the current-state doc and the completion journal. Establish what the product actually does now before writing a word of narrative. If the current-state doc itself is stale, revising it is the session's artifact.
Draft the narrative for the README, site, or current-state doc so that each capability claim names a real, landed capability. Keep it legible and honest; resist the pull toward aspirational language that outruns current state.
For each capability claim in the rendering, confirm it traces to a current-state entry. Cut or defer any claim that has no anchor — an unanchored claim is not publishable, however true it may feel.
Declare the mode (communicating) in the session record and list the README,
site, or current-state revision as the produced or revised artifact.
The README and site are living documents the lead-pm stewards and revises in place; the current-state doc is their anchor. Product communication is in scope; the parked GTM disciplines are not — if the product authority needs positioning, pricing, or growth metrics, name the gap and route it rather than improvising it here.
