asb-carol-observations

Facilitates structured gathering of raw company observations into a numbered OBSERVATIONS.md file.

Updated Nov 15, 2025
One-click install
npx skills add https://github.com/evanish/reusable-PM-templates --skill asb-carol-observations-evanish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asb-carol-observations
Source: https://github.com/evanish/reusable-PM-templates/tree/main/Templates%20to%20reuse/Work/asb-customer-discovery/asb-carol-observations
Command: npx skills add https://github.com/evanish/reusable-PM-templates --skill asb-carol-observations-evanish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Defining an ideal customer profile starts with an honest accounting of what a company actually is, but asking people to list strengths and weaknesses produces vague, defensive answers. This Skill runs the first step of a proven ICP method: gathering raw, specific, unjudged observations about the company, product, customers, and team before any classification happens. ## Core Features & Use Cases - Twelve-Category Guided Walk: Walks the user one category at a time through twelve question areas (undeniable strengths, consistent complaints, head/tail customer differential, existential threats, technical architecture, philosophy, and more), pressing vague answers into specific, checkable facts. - Team Write-Storm Processing: Ingests a team's raw brainstorm notes and processes each observation individually — clarifying, sharpening, merging duplicates, and filing under the right category. - External Research Seeding: For companies already operating online, scans public reviews, forums, and press into an External Research section that seeds candidate observations for user confirmation. - Use Case: A founder asks "who is our ideal customer?" The Skill walks them through twelve categories, records numbered observations (O1, O2, ...) in OBSERVATIONS.md, parks action ideas in a side-list, and hands off to the next method step that classifies attributes as strengths or weaknesses. ## Quick Start Ask the assistant to run the asb-carol-observations skill to start gathering honest observations about your company for defining your ideal customer profile.

Frequently Asked Questions about asb-carol-observations

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start defining an ideal customer profile for my company?

Start by gathering raw observations about what your company actually is before judging strengths or weaknesses. This Skill walks you through twelve question categories — from consistent complaints to head/tail customer differences — and records each specific, checkable fact in an OBSERVATIONS.md file.

How do I run a strengths and weaknesses exercise with my team?

Have the team write-storm observations individually first, then process the notes one at a time: clarify each entry, sharpen it into a specific fact, merge duplicates, and file it under a category. Classification into strengths and weaknesses is a separate later step.

Can this skill process existing customer reviews and public feedback?

Yes. For companies already operating online, it scans public reviews, social posts, forums, and press into an External Research section. Each finding becomes a candidate observation that the user must confirm before it is promoted to a numbered observation.

What happens if I resume an unfinished observations session?

The OBSERVATIONS.md file carries an in-progress header naming the current category or team-dump position. On resume, the Skill reads the file, confirms the state, and continues from that pointer without re-asking setup questions or re-eliciting recorded observations.

When should I not use this observations-gathering skill?

Do not use it to classify observations into strengths and weaknesses — that is the next method step with its own rubric. It also does not fit personal self-reflection unrelated to a company, or sessions that mix two different companies into one file.