/arn-spark-stress-prfaq

name: arn-spark-stress-prfaq
description: >-
  This skill should be used when the user says "prfaq", "pr faq", "pr/faq",
  "press release stress test", "stress prfaq", "amazon pr faq method",
  "test the pitch with a pr/faq", "validate concept through pr/faq",
  "critique press release", "pr faq stress test",
  "will this marketing story hold up", or wants to stress-test a product concept by drafting a
  compelling press release and FAQ, then adversarially critiquing it to find
  where the concept cracks under scrutiny. Produces a PR/FAQ report with the
  full draft, adversarial questions, crack point analysis, and recommended
  concept updates.
version: 1.0.0

Arness Spark Stress PR/FAQ

Stress-test a product concept using Amazon's PR/FAQ method. This technique forces the product concept through two filters:

1. **Draft phase:** A marketing PM agent writes the best possible public story -- a compelling press release, customer FAQ, and internal FAQ. If the press release is unconvincing, the product concept likely has clarity problems. 2. **Critique phase:** The same marketing PM agent (in a separate invocation, with no memory of drafting) adversarially attacks the draft -- finding questions the PR dodges, identifying crack points where claims exceed substance, and recommending concept changes.

The two phases use **separate agent invocations** to prevent rubber-stamping. A critic who remembers being the drafter unconsciously defends what it wrote. Separate invocations force genuine adversarial evaluation.

The product concept is read but never modified -- all recommendations are captured in the PR/FAQ report for later review.

Prerequisites

Configuration Check

1. Read the project's `CLAUDE.md` and check for a `## Arness` section 2. If found, extract the configured **Vision directory** and **Reports directory** paths 3. If no `## Arness` section exists or Arness Spark fields are missing, inform the user: "Arness Spark is not configured for this project yet. Run `/arn-brainstorming` to get started — it will set everything up automatically." Do not proceed without it. 4. If the Reports directory does not exist, create it with `mkdir -p <reports-dir>/stress-tests/`

Data Availability

| Artifact | Status | Location | Fallback | |----------|--------|----------|----------| | Product concept | REQUIRED | `<vision-dir>/product-concept.md` | Cannot proceed without it -- suggest running `/arn-spark-discover` | | Product pillars | ENRICHES | Product Pillars section of product concept | Draft messaging is less focused; critique has fewer anchors | | Competitive landscape | ENRICHES | Competitive Landscape section of product concept | Draft positioning is less grounded in market context | | Target personas | ENRICHES | Target Personas section of product concept | Customer quote in press release is less persona-specific |

**Standard fallback cascade:**

If no product concept exists:

Ask (using `AskUserQuestion`): **"No product concept found. The PR/FAQ stress test needs a product concept to draft and critique messaging for. How would you like to proceed?"** 1. Run `/arn-spark-discover` to create a product concept first 2. Describe the product now (I will conduct the PR/FAQ from your description) 3. Skip the PR/FAQ stress test

If the user chooses option 2, collect a product description and proceed with a reduced-fidelity test (note in the report that the test was based on a verbal description rather than a full product concept).

Workflow

Step 1: Load References

Load the PR/FAQ workflow and report template: > Read `${CLAUDE_PLUGIN_ROOT}/skills/arn-spark-stress-prfaq/references/prfaq-workflow.md` > Read `${CLAUDE_PLUGIN_ROOT}/skills/arn-spark-stress-prfaq/references/prfaq-report-template.md`

Step 2: Read Product Concept and Extract Context

Read the product concept from `<vision-dir>/product-concept.md`. Extract:

• Full product concept (both draft and critique need the complete document)
• Product pillars (anchors messaging in draft, tested for sincerity in critique)
• Competitive landscape (grounds positioning in real market context)
• Target personas (for realistic customer quote in press release)
• Core experience (primary material for the solution paragraph)

Step 3: Phase 1 -- Draft

Invoke the `arn-spark-marketing-pm` agent in **draft mode** via the Task tool, passing the model from `.arness/agent-models/spark.md` as the `model` parameter (see `plugins/arn-spark/skills/arn-spark-ensure-config/references/ensure-config.md` "Dispatch convention" for fallback). Context:

--- PRODUCT CONCEPT --- [full product concept document] --- END PRODUCT CONCEPT ---

--- PRODUCT PILLARS --- [product pillars section] --- END PRODUCT PILLARS ---

--- OPERATING MODE --- draft --- END OPERATING MODE ---

Receive back the complete draft: press release (400-600 words), customer FAQ (5-8 entries), internal FAQ (3-5 entries).

**Quality check before proceeding:**

• Press release must be 400-600 words and compelling (would a reporter find this newsworthy? Does it lead with customer value, not features?)
• Customer FAQ answers must be concrete with specific examples, not evasive hedging
• Internal FAQ questions must address genuine tensions or risky claims in the press release
• Customer quote must use colloquial language and personal emotion, not corporate phrasing

If the draft is too thin or generic, retry with more specific context:

"The draft needs to be more specific. Ground it in these details:

• Target persona for the customer quote: [specific persona from product concept]
• Key competitive differentiator: [from competitive landscape]
• Core interaction to highlight: [from core experience]
• Most important pillar to anchor messaging: [from product pillars]"

Step 4: Phase 2 -- Critique

Invoke the `arn-spark-marketing-pm` agent in **critique mode** via the Task tool, passing the model from `.arness/agent-models/spark.md` as the `model` parameter (see `plugins/arn-spar