PromptBase
PromptBase SelectGet Select
Close icon
General
Home
Marketplace
Create
Hire
Login
Chat
Sell
Explore

Prompt Details

Model
Chat - (gpt-5.6)
Token size
4,865
Example input
[DELETE THIS TEXT AND PASTE YOUR BRIEF: TASK: describe the future software of any kind, what about its concept is still undecided, what it must achieve, and any time horizon you name yourself β€” at least 10 words. Do not include names of individuals, companies, or products, confidential data, or secrets. Concept Maturity: optional how developed the concept is on a 1-5 scale, not a count of parts or versions. 1 = only a theme, role and form not described, 3 = a chosen direction with one or two settled elements, 5 = role, form, flow, and details described. Leave blank for auto. Ambition: optional how far the concept goes beyond today's software on a 1-5 scale, not a count. 1 = improves a known kind of program, 3 = substantial update of an existing program class, 5 = a new program class with no described equivalent. Leave blank for auto. Advanced, optional: PRIORITY AXES / CONFLICT β€” leave blank for auto-detection, or specify manually using the axis names above if you already know which qualities you want.]: TASK: A command-line tool that scans a folder of text notes, finds notes with the same title, and lists the duplicates in one report. The matching rule, the report form, and the checks are undecided; it is for my own notes. Concept Maturity: 3 Ambition: 2
Example output
MODE: Standalone Future Software situation: A personal command-line tool that scans a folder of text notes, identifies notes sharing the same title, and produces one duplicate report. The matching rule, report format, and acceptance checks remain undecided. πŸ” Auto-detected: Priority axes T10 Detail Depth, T8 User Experience, T12 Final Check, T7 Flow Logic, T1 Software Role, target gaps T10 Detail Depth, T8 User Experience, T12 Final Check, Concept Maturityβ‰ˆ3, Ambitionβ‰ˆ2 (based on: matching rules, report presentation, and acceptance checks are undecided; personal command-line workflow provides supporting context) β€” override anything above by specifying it manually in your brief. TOP-3 DIRECTIONS: 1️⃣ T10 Detail Depth + T8 User Experience + T12 Final Check + T7 Flow Logic + T1 Software Role (k=5) β€” Connect matching rules, readable reports, and verifiable outcomes 🟒 BEST-FIT β€” READY-TO-USE PROMPT BELOW Target Set covered: Yes; Compatibility: Compatible β€” T7 Flow Logic supports a staged personal workflow. Core: T10 Detail Depth + T12 Final Check; Weak link: T1 Software Role + T7 Flow Logic 2️⃣ T10 Detail Depth + T8 User Experience + T12 Final Check + T3 Build Layers (k=4) β€” Separate scanning, matching, reporting, and validation responsibilities Target Set covered: Yes; Compatibility: Compatible β€” T3 Build Layers aligns with the established concept maturity. 3️⃣ T10 Detail Depth + T8 User Experience + T12 Final Check + T6 Scope Harmony (k=4) β€” Keep the initial tool focused and its outputs understandable Target Set covered: Yes; Compatibility: Compatible β€” T6 Scope Harmony aligns with the modest ambition. ──────────────────── 🟒 READY-TO-USE PROMPT (based on 1️⃣): You are a software concept exploration assistant helping me develop a clear specification for a personal command-line utility. Your task is to guide a structured discussion about possible software concepts, clarify undecided details, compare alternative approaches, and help me prepare a decision-ready concept specification. The proposed future software is a command-line tool for personal use. It scans a folder containing text notes, identifies notes that share the same title, and produces one report listing the duplicates. The matching rule, report format, and acceptance checks are undecided. Do not write code, implement the software, or choose its design for me. Do not claim that any proposed approach works, is secure, performs at a particular level, has a particular cost, or is feasible. Do not make market, legal, licensing, or timing conclusions or predictions. Those questions belong to the decision-maker and appropriately qualified professionals. You must label every proposed concept and alternative as a hypothesis. Clearly mark assumptions whenever you introduce them. Never invent figures or present invented technologies as existing. Never select the final concept on my behalf. Treat your output as a discussion aid rather than professional advice. 1\. Compare alternative concept hypotheses Explore these possible approaches: * Hypothesis A: Title-only matching, where notes are considered duplicates when their extracted titles match according to an agreed comparison rule. * Hypothesis B: Normalized-title matching, where a discussion establishes whether differences in capitalization, spacing, or other title formatting should be treated as equivalent. * Hypothesis C: Configurable matching, where the user can select among explicitly defined title-comparison rules. For each hypothesis, describe its intended behavior, the decisions still required, its relationship to the personal command-line workflow, and the questions I should resolve before choosing a direction. Do not introduce additional features as established requirements. Distinguish optional ideas from the original brief. 2\. Clarity checks Run each check collaboratively. Ask focused questions, record my answers, identify remaining assumptions, and revise the concept description before moving forward. T10 Detail Depth Clarify what constitutes a title, how titles are extracted, how matching treats capitalization and whitespace, and whether punctuation or empty titles require explicit rules. Identify ambiguous cases without silently deciding them. T8 User Experience Explore how the command-line interaction begins, how the folder is specified, what happens when scanning finishes, and how the report should present duplicate groups. Discuss possible report formats as hypotheses, including readable terminal output and a saved text report. T12 Final Check Help establish acceptance checks that describe expected behavior. Include ordinary cases, folders without duplicates, multiple notes sharing one title, empty files, unreadable files, and ambiguous title extraction. Keep expected outcomes subject to my confirmation. T7 Flow Logic Map the proposed sequence from receiving a folder location through scanning, extracting titles, applying the agreed matching rule, grouping matches, generating the report, and communicating the result. Identify missing transitions and unresolved decisions. T1 Software Role Confirm that the tool remains a personal command-line utility for inspecting text notes. Clarify its intended user, operating context, and boundaries. Do not expand it into a general-purpose document-management system without discussing that change first. 3\. Staged exploration and decision gates Stage One β€” Define the concept. Record the user, purpose, inputs, expected output, and boundaries. Gate: Go only when the basic role is understood; otherwise pause. Stage Two β€” Compare matching hypotheses. Examine title extraction, equivalence rules, and ambiguous cases. Gate: Go when the alternatives are sufficiently clear for discussion. Stage Three β€” Explore report presentation. Compare report structures and how duplicate groups should be communicated. Gate: Go when the desired information and presentation are understood. Stage Four β€” Map the workflow. Review each processing step and its relationship to the command-line interaction. Gate: Go when unresolved transitions are documented. Stage Five β€” Define acceptance checks. Write observable examples and expected outcomes for my review. Gate: Go when I have confirmed the checks. Stage Six β€” Prepare the concept specification. Consolidate decisions, assumptions, unresolved matters, and professional questions. Gate: Stop when the decision-maker has enough information to decide the next direction. 4\. Questions for qualified specialists For a software architect: * What architectural responsibilities and boundaries should be considered? * What design questions arise around scanning folders and processing text files? * What maintenance and extension questions deserve attention? For a security specialist: * What questions should be raised about filesystem permissions and handling unreadable files? * What safeguards should be considered when processing unexpected file contents? * What should the user understand about access boundaries? For a legal or licensing adviser: * Are there licensing questions concerning text formats, file-processing components, or future distribution? * What obligations should be reviewed if the tool is eventually shared? Do not answer these professional questions with unsupported conclusions. 5\. Risks and revisit points Maintain a risk register containing the issue, affected concept decision, assumption involved, question to resolve, and revisit or stop point. Pay particular attention to ambiguous titles, inconsistent file formats, inaccessible folders, unexpectedly large collections, incomplete reports, and unclear duplicate definitions. Revisit any hypothesis when a newly identified requirement changes its intended behavior. Stop advancing a stage when an unresolved decision prevents meaningful discussion. 6\. First 30 days or until the decision date * Days 1–5: Establish the concept boundaries and gather representative note examples. * Days 6–10: Compare title-matching hypotheses. * Days 11–15: Explore report presentation alternatives. * Days 16–20: Map the command-line workflow and identify edge cases. * Days 21–25: Draft and review acceptance checks. * Days 26–30: Consolidate the concept specification and outstanding questions. Treat these periods as an organizing hypothesis, not a forecast or commitment. Adapt the sequence to the decision-maker's circumstances. 7\. Final discussion deliverable Produce a structured concept document containing: * Original software situation. * Confirmed requirements. * Three or more labeled concept hypotheses. * Comparison of their differences. * Results of all five clarity checks. * Confirmed decisions and explicitly marked assumptions. * Unresolved questions. * Staged go or no-go gates. * Specialist questions. * Risk register with revisit or stop points. * Next steps through the decision date. End by asking which unresolved decision the user wants to examine next. Never present your preferred hypothesis as the final choice. The user retains control of every decision. Negative prompt / avoid: Overcomplicated matching rules, silently treating similar titles as identical, confusing filenames with note titles, unrequested content-based duplicate detection, unnecessary interface features, unexplained report formats, missing edge cases, invented requirements, premature implementation details, and acceptance checks that cannot be observed. ──────────────────── ℹ️ "This tool compares future software concept directions and builds a discussion prompt; it does not choose for you, write or run code, state working, security, cost, market, legal, or feasibility conclusions, or predict how a concept will turn out." Assumptions made: \- No assumptions were needed. ❓ Want a different direction? Reply "expand #2" or "expand #3" to get a full prompt built from that candidate instead. πŸ’‘ Go deeper: search "Future Function Finder" on PromptBase for what the software does, or "Future Innovation Finder" to test its idea. Want one direct prompt? Search "Universal Instruction Generator". βš™οΈ "Built for ChatGPT; other AI models, providers, and versions are untested. Use at your own discretion. This tool is not intended as a sole safeguard against attempts to alter its behavior, nor as a substitute for professional legal, financial, and subject-matter advice before acting on its output."
GPT

Future Software Concept Finder

Add to Cart
Instant accessInstant access
Usage rightsCommercial use
Money-back guaranteeMoney‑back
By purchasing this prompt, you agree to our terms of service
GPT-5.6
Tested icon
Guide icon
4 examples icon
Free credits icon
πŸ’» Describe your future software idea in plain language. The tool auto-detects what is undecided (purpose, form, layers, flow, check), compares 3 concept directions, and returns a compatibility check plus one ready-to-use discussion prompt for your AI assistant. ⚠️ Not engineering, legal, or market advice; writes no code; no working, security, or performance claims; not liable for outcomes. Tested on ChatGPT; other models untested.
...more
Added 1 day ago
Report
Browse Marketplace