feature-blueprint
Feature specification
Given a feature idea, an agent builds the happy path and fills in the rest silently and badly: "No data" with no next step, an endless spinner, a double charge after a double click, backups nobody ever restored from, a sync that quietly stopped a month ago. You know how to avoid all of this. This skill sets the order in which to think of it in time, how to work with the owner, and the document format. The owner's explicit instruction in the conversation and the owner's own rules, global or the project's, take precedence over this skill.
Language. This skill is in English. Everything the owner reads — the specification with the template's headings, summaries, questions, plan lines, issues and comments, markers — is written in the language the owner uses in the conversation. File, function and field names, commands, paths, error codes, product names and section numbers stay as they are.