specsafe-explore

Guide pre-specification exploration with problem understanding, research, prototyping, and documentation.

3|Updated Jan 27, 2026

Search Tags:#research #requirements #prototyping #feasibility #exploration #spike

Ready to run

npx skills add https://github.com/Agentic-Engineering-Agency/specsafe --skill specsafe-explore

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: specsafe-explore
Source: https://github.com/Agentic-Engineering-Agency/specsafe/tree/main/.claude/skills/specsafe-explore
Command: npx skills add https://github.com/Agentic-Engineering-Agency/specsafe --skill specsafe-explore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps clarify requirements and technical feasibility by providing a structured approach to pre-specification research and prototyping, preventing wasted effort on ill-defined or unfeasible features.

Core Features & Use Cases

Requirement Clarification: Helps understand the core problem, stakeholders, and constraints.
Solution Research: Explores existing solutions, best practices, and available libraries.
Feasibility Spikes: Facilitates optional prototyping to test technical assumptions.
Documentation: Guides the creation of exploration notes, findings, and recommendations.
Use Case: Before committing to building a complex new feature, use this Skill to research different architectural approaches, evaluate third-party integrations, and create a small proof-of-concept to ensure the chosen path is viable.

Quick Start

Use specsafe-explore to research the feasibility of adding real-time collaboration features.

Frequently Asked Questions about specsafe-explore

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

FAQPage Schema

How do I assess technical feasibility before writing a feature specification?▼

To assess technical feasibility before writing a feature specification, you should conduct pre-specification exploration by researching existing solutions, evaluating options with pros and cons, and running optional prototyping spikes to test assumptions. This process prevents wasted development effort on unviable requirements.

What is a feasibility spike and when do I need one for new feature development?▼

A feasibility spike is an optional prototyping step used during pre-specification exploration to test technical assumptions for new feature development. You need one when evaluating unclear requirements or unproven technical integrations to ensure the chosen architectural path is viable before committing to a full build.

How do I research existing solutions and libraries before committing to a complex feature build?▼

To research existing solutions and libraries before committing to a complex feature build, guide your team through structured problem understanding, evaluate available options with documented pros and cons, and estimate the effort required. This structured exploration ensures you recommend a viable path forward.

What is the best way to document pre-specification exploration findings for a new software feature?▼

The best way to document pre-specification exploration findings is to guide the creation of structured exploration notes that record problem understanding, research findings, feasibility assessments, and effort estimates. This documentation clarifies requirements and recommends a clear path forward for development.

How do I clarify ill-defined requirements before starting software development?▼

To clarify ill-defined requirements before starting software development, engage in pre-specification research to understand the core problem, identify stakeholders, and outline constraints. This structured approach prevents wasted development effort on features that are technically unfeasible or poorly defined.