Surface and categorize assumptions underlying product strategy. Use early in development to document what you're betting on.
The English summary is being prepared. Showing the original description.
itseffi/agentic-os117Updated Oct 7, 2026
FreePublished on GitHub
signal-identification
Design efficient early signals to validate assumptions. Find the fastest way to learn if you're right.
The English summary is being prepared. Showing the original description.
See how to installFiles included (2)
- SKILL.md1.9 KB
- agents/openai.yaml187 B
SKILL.md (original)
Review the instructions the agent will receive before you install.
Signal Identification
Design efficient early signals to validate product assumptions.
When to Use
When you have a prioritized assumption and need the fastest way to validate it.
The Quality Bar
A good signal is:
- Early: Obtainable at idea/prototype stage
- Cheap: Minimal cash/time
- Attributable: Directly reduces uncertainty
- Decisive: Has clear success/failure threshold
- Suitable: Appropriate for your context
Method Selection by Context
| Context | Good Methods | Avoid |
|---|---|---|
| Enterprise B2B | Design partner LOIs, security questionnaires, ROI calculators, reference checks | Smoke tests, consumer ad funnels |
| SMB SaaS | Discovery calls, lightweight trials, email tests, usage analytics | - |
| Consumer | Ad-driven intent, waitlist conversion, community polls, preorders | - |
| Regulated | Standards mapping, SME review, regulatory preflight | Collecting sensitive data |
| Feasibility | Engineering spikes, benchmarks, vendor evals | User-facing experiments |
The Process
1. Classify the Assumption
What lens? Desirability, Feasibility, Viability, or Usability?
2. Brainstorm Signals (5+)
For each, note:
- What would constitute positive evidence?
- How to obtain quickly?
- Why suitable for this context?
3. Select Best Signal
Document:
- Signal description
- Method (step-by-step)
- Participants/sample needed
- Timebox and cost
- Success threshold (quantified)
- Data captured
- Risks and mitigations
- What to do next if positive
Output
- Brainstorm list (5+ signals)
- Selected signal with full details
- Summary explaining choice
When Not to Use
Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.
Reviews
No reviews yet. Tell others what you thought.
Comments
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
More skills from this repository
Prioritize assumptions by risk and importance. Use after assumption mapping to decide what to test first.
The English summary is being prepared. Showing the original description.
itseffi/agentic-os117Updated Oct 7, 2026
Sync Jira issues with local tasks. Use during daily planning or when user asks about Jira issues.
The English summary is being prepared. Showing the original description.
itseffi/agentic-os117Updated Oct 7, 2026
backend-design
FreeDesign backend architecture for implementation with API contracts, data model changes, service boundaries, security, and observability.
The English summary is being prepared. Showing the original description.
itseffi/agentic-os117Updated Oct 7, 2026
brainstorming
FreeTurn ideas into designs through collaborative dialogue. Use before any creative work - features, components, or modifications.
The English summary is being prepared. Showing the original description.
itseffi/agentic-os117Updated Oct 7, 2026
Check Google Calendar for today's schedule. Use during daily planning or when user asks about their calendar.
The English summary is being prepared. Showing the original description.
itseffi/agentic-os117Updated Oct 7, 2026