What problem does it solve? Turning a clarified requirement into an implementation-ready technical design is slow and error-prone when the agent lacks project conventions. This Skill reads the project's .Knowledge/ topics, stock docs, and design template to produce a technical design document that matches existing naming, error-code, data, and module-boundary conventions. ## Core Features & Use Cases - Clarification gate: Refuses to write a design from vague input and routes to f2s-req-clarify first, or lists the 3-6 blocking questions. - Knowledge-grounded drafting: Loads relevant .Knowledge/topics/ and .Knowledge/stock-docs/ content and assembles the document from the optional building blocks in .Knowledge/template/技术方案模版.md. - Optional sub-agent split: When subAgent=true, the main agent first produces a project-conventions summary (under 80 lines) covering contracts, error codes, async integration, data storage, structure, and module boundaries before delegating drafting. - Use Case: After clarifying a new feature requirement, invoke this Skill to produce .Knowledge/req-docs/<name>_技术方案.md that developers can implement directly, for backend, frontend, full-stack, mobile, or scripting work. ## Quick Start Ask the agent to generate a technical design from the clarified requirement document at .Knowledge/req-docs/my-feature_需求澄清.md using the f2s-req-tech skill.
