propose

Evaluate software ideas and generate formal proposal documents.

30|1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/pacaplan/flokay --skill propose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: propose
Source: https://github.com/pacaplan/flokay/tree/main/skills/propose
Command: npx skills add https://github.com/pacaplan/flokay --skill propose

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you rigorously evaluate whether a new software idea is worth pursuing and, if so, guides you in creating a clear proposal document that articulates the "why."

Core Features & Use Cases

  • Idea Evaluation: Assesses the significance of a problem, explores alternatives, and considers opportunity costs.
  • Approach Exploration: Lightly sketches the high-level architecture, key technical decisions, and scope bounding.
  • Proposal Generation: Writes a "why" document focusing on motivation, problem, opportunity, and impact.
  • Use Case: Before committing development resources, use this Skill to get a clear, research-informed assessment of a new feature request, ensuring it aligns with business goals and is technically feasible.

Quick Start

Use the propose skill to evaluate the idea of adding real-time collaboration to the document editor.

Frequently Asked Questions about propose

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

FAQPage Schema
How do I evaluate if a software idea is worth pursuing before implementation?

A feasibility study for software development assesses problem significance, explores existing alternatives, and considers opportunity costs. It articulates the motivation behind an idea and bounds its scope before any implementation resources are committed.

How do I write a proposal document for a new software feature?

To write a software proposal document, research existing specifications and codebases, explore high-level technical approaches, and document the motivation, problem, opportunity, and impact. This focuses on articulating the 'why' behind the feature request.

What is the best way to document the motivation and scope for a new product feature?

The best way to document motivation and scope is by creating a formal proposal that articulates the problem, explores high-level architecture, and bounds the technical decisions. This ensures the development team understands the purpose and limitations before starting.

Can I use this approach to assess technical feasibility for a real-time collaboration feature?

Yes, you can assess technical feasibility for a real-time collaboration feature by lightly sketching the high-level architecture, identifying key technical decisions, and bounding the scope. This research-informed assessment ensures the feature is viable.

When should I not move directly into software development for a new idea?

You should not move directly into software development when the problem significance is low or viable alternatives already exist. Conducting an idea evaluation first helps identify opportunity costs and risks, preventing wasted resources on poorly scoped projects.