spec-ask

Prompt users with preference-driven questions and document decisions in a research file.

9|Updated May 27, 2026
One-click install
npx skills add https://github.com/kamioj/spec-workflow --skill spec-ask
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-ask
Source: https://github.com/kamioj/spec-workflow/tree/main/codex/skills/spec-ask
Command: npx skills add https://github.com/kamioj/spec-workflow --skill spec-ask

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps streamline decision-making processes by asking specific, preference-driven questions to ensure that all necessary decisions are made and documented thoroughly.

Core Features & Use Cases

  • Decision Interrogation: Works through each open decision point one by one, ensuring no important considerations are overlooked.
  • User-Driven: Allows users to provide their preferences and rationale, fostering a collaborative decision-making process.
  • Documentation: Automatically documents decisions and rationales in a research file for future reference.

Quick Start

Trigger the spec-ask skill to start the decision-making process.

Frequently Asked Questions about spec-ask

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

FAQPage Schema
How do I document software development decisions and rationales for project planning?

You can document software development decisions by triggering the decision-making process, which prompts for specific preferences and rationales, then automatically records them in a research file for future reference.

What is targeted questioning for decision-making in software development?

Targeted questioning for decision-making is a process that works through open decision points one by one, asking preference-driven questions to ensure no important considerations are overlooked in project planning.

Can I use structured decision documentation for feature selection and resource allocation?

Yes, structured decision documentation is suitable for feature selection and resource allocation in software development, allowing users to provide preferences and rationale for each decision point.

What's the best way to ensure no important decisions are overlooked during project planning?

The best way to ensure no decisions are overlooked is to use a decision interrogation process that works through each open decision point sequentially, prompting for user preferences and rationale.

Why does my project planning lack documented rationales for feature selection decisions?

Project planning often lacks documented rationales because decisions are made informally, whereas a structured question-driven process automatically documents both the decisions and their underlying rationales in a research file.