MODE: Standalone Future Software Build situation: A personal command-line tool for finding duplicate note titles 🔍 Auto-detected: Priority axes K10 Detail Depth, K8 User Experience, K12 Final Check, K7 Flow Logic, K3 Build Layers, target gaps K10 Detail Depth, K8 User Experience, K12 Final Check, Concept Maturity≈3, Ambition≈2 (based on: matching rules, report form, and acceptance checks undecided; core scanning workflow described) — override anything above by specifying it manually in your brief. TOP-3 DIRECTIONS: 1️⃣ K10 Detail Depth + K8 User Experience + K12 Final Check + K7 Flow Logic + K3 Build Layers (k=5) — Clear matching rules, readable reports, and independently checkable results 🟢 BEST-FIT — BUILD PACK BELOW Target Set covered: Yes; Compatibility: Compatible — K7 Flow Logic fits the defined scanning workflow and both scale levels. Core: K10 Detail Depth + K8 User Experience; Weak link: K3 Build Layers + K7 Flow Logic 2️⃣ K10 Detail Depth + K8 User Experience + K12 Final Check + K5 Lasting Use + K6 Scope Harmony (k=5) — Reusable note scanning with a deliberately controlled feature scope Target Set covered: Yes; Compatibility: Compatible — K5 Lasting Use aligns with the maturity and modest ambition levels. 3️⃣ K10 Detail Depth + K8 User Experience + K12 Final Check + K1 Build Role + K4 Data Link (k=5) — Focused personal workflow with clearly connected folder inputs and reports Target Set covered: Yes; Compatibility: Compatible — K1 Build Role matches the defined personal use case and maturity. ──────────────────── 🟢 BUILD PACK (based on 1️⃣): Working title: Note Title Duplicate Finder Copy each field marked COPY into your AI assistant in one message; the follow-up lines are for you only. ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ 🛠️ BUILD BRIEF — COPY first: Goal: Create a personal command-line tool that scans a folder of text notes, identifies notes sharing the same title, and presents them in one readable duplicate report. Language: Python using standard-library modules first. Inputs: One folder path supplied as a command-line argument. Read plain text files directly inside that folder without modifying them. Outputs: A readable terminal report grouping matching titles and listing the corresponding filenames and paths. Clearly report when no duplicates are found. Step 1: Accept and validate the supplied folder path. Step 2: Identify readable plain text files in the folder. Step 3: Extract each note's title from its first non-empty line. Step 4: Normalize titles by trimming surrounding whitespace, collapsing repeated internal whitespace, and ignoring capitalization when comparing. Step 5: Group files with matching normalized titles while preserving their original displayed titles. Step 6: Display one report containing each duplicate title and its associated filenames, followed by a total group count. Constraints: No network calls, additional installations, or file deletions. Do not modify source notes. Scan only the supplied folder, not subfolders. Handle empty folders, unreadable files, missing paths, and notes without titles gracefully. Delivery: Provide the complete program in one Python file with comments and a command-line usage example. ┈┈┈┈┈┈┈┈┈┈┈┈┈┈ ✅ ACCEPTANCE CHECKS — COPY right after the build brief: a. A folder containing three notes, two titled Meeting Notes and one titled Shopping List, produces one duplicate group listing the two matching filenames. b. Two notes titled Project Plan and project plan are grouped together, ignoring capitalization. c. Two notes titled Weekly Report and Weekly Report are grouped together after whitespace normalization. d. An empty folder produces a clear message indicating that no duplicate titles were found. e. A nonexistent folder path produces a helpful error message without crashing or modifying files. ┈┈┈┈┈┈┈┈ 🚫 DO NOT LIST — COPY right after the checks: Do not use real secrets, keys, passwords, or personal data, call services the brief does not name, delete or overwrite files, leave the code unfinished, modify original notes, scan subfolders, silently ignore unreadable files, or treat filenames as note titles. ┈┈┈┈┈┈┈ 🔧 FOLLOW-UP LINES — do NOT copy, a guide for you: Add an optional setting that lets me choose how duplicate titles are matched. Show me an example terminal report using five sample notes, including two duplicate groups. Review the program against every acceptance check and identify any missing cases. ──────────────────── ℹ️ "This tool compares future software concept directions and builds a paste-ready pack of a build brief, acceptance checks, and a do-not list; it does not write or run code, choose for you, state working, security, performance, cost, market, legal, or feasibility conclusions, or predict how a concept or an assistant will turn out." Assumptions made: * Language: Python, because no programming language was specified. * Title rule: First non-empty line, normalized for capitalization and whitespace. * Report form: One grouped terminal report, because no report format was specified. ❓ Want a different direction? Reply "expand #2" or "expand #3" to get a full pack 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."