yanhaoluo0/technical-proposal-expert-writing-skill

Chinese official document writing skills: Technical proposal, solution design report, test report, weekly report; Other documents follow the usual bottom line. The root directory SKILL.md is the only entry point; skill internally treats it as a mandatory instruction set.

Why do we have it?

When writing technical proposals and design reports, the most common quality issue is “superficial”: the implementation plan only has conceptual terms (microservices, high availability, big data), without reasons for selection, mechanism details, or indicator support. This skill solves this problem with three things:

1. Built-in Knowledge Base (knowledge/): ‘Technical cards’ organized by technical domain, selectively searched by technical points/indicator keywords during writing, only reading hit chapters to save context
2. Project Material Library (素材库/ under the writing directory): Insert bidding document excerpts, technical specifications, historical bidding documents, etc. into the project catalog. When writing, read the full text to ensure the content is relevant to the actual project context; No global material library is established; materials are retained or cleaned after the project is completed
3. Six Questions on In-depth Writing: For each key technical point, you must answer ‘What problem is solved / Why choose this / Key mechanisms and data flow / Engineering implementation / How to verify / Risk and de-escalation.’ It is forbidden to use modifiers to replace substance

Additionally, constraints such as zero scoring points (no point breaks in the tender document), banned word list, “pending confirmation” not fabricated, and pre-delivery review checklists, ensure output is formatted, in-depth, and verifiable.

Installation

Clone the entire repository to the skills directory, and unify the installation directory names to technical-proposal-expert**:

Each tool only contains one copy. The old software-engineering-docs name has been obsolete. Please delete the old copy to avoid listing “two skills.”

If not autoloading, say in dialogue: 使用 technical-proposal-expert 写【文档类型】.

Usage Process

Just state the document you want to write, such as “write technical proposal,” “produce design report,” “write test report,” or “write weekly report.” When unclear about the type, it will first ask about the scenario, then read the corresponding references/.

Material Retrieval (Core Usage)

The two sources of content have different rules:

Usage steps:

1. Create 素材库/ in the Writing Project Working Directory (the 素材库/ in this repository is only templates and instructions), and place the materials you want to refer to (only .md / .txt, which can create subdirectories). It is recommended to include: Tender Document Excerpts, Technical Specifications, Historical Bidding Documents, Architecture Description, and General Technical Documentation.

2. Generate index (no parameters required, automatically scans skill’s knowledge/ and ‘current working directory’ 素材库/):