development-planning-writer

Development Planning Writer

A writing skill for regional development plans and local special plans for governments, parks, public institutions, and consulting and research institutions.

It is not a general-purpose "industry article generator", nor a tool for ghostwriting investment promotion slogans or corporate strategy PPTs. The goal is to produce a working draft closer to a formal planning text: clear planning attributes, complete basis, quantifiable objectives, closed loops between tasks and projects, and implementable implementation paths and evaluation mechanisms.

What to read first

• First read references/planning-rules.md, to confirm the statutory attributes, drafting procedures, hard constraints, and common rigid requirements.
• Before drafting the main text, read by plan type references/structure-templates.md。
• Before designing objectives, indicators, the project library, and the implementation matrix, read references/indicator-and-projects.md。
• When mature writing approaches, chapter organization, or indicator expressions need to be referenced, read references/example-patterns.md。
• Before finalizing, read references/self-checklist.md。

Applicable tasks

• Draft 区域发展规划
• Draft 地方专项规划
• Draft the “十五五”规划
• Draft plan 编制说明、征求意见稿、专家论证稿
• Design 指标体系、重大项目清单、重点任务分工表
• Rewrite an existing draft plan after supplementing it with higher-level plans, the latest policies, statistical data, and benchmarking cases

Not intended by default for:

• Corporate business strategy
• Business plans
• Investment and financing roadshow materials
• Investment promotion publicity copy
• Territorial spatial master plans or detailed plans
• Simple news releases, speech drafts, or publicity articles

Automatic type determination

First determine whether it is regional or specialized, then start writing:

• regional: The object is a "specific region" such as a cross-administrative region, metropolitan area, city cluster, sub-district, park coordination zone, or economic belt along a route; focus on strategic positioning, spatial pattern, functional division, coordination mechanisms, cross-regional projects, and public service/ecological/security coordination.
• specialized: The object is a "specific field" such as education, science and technology, industry, transportation, culture and tourism, elderly care, digitalization, or the ecological environment; focus on development foundations, overall requirements, indicator systems, key tasks, major engineering projects, and safeguard measures.

If the user gives a vague topic, first fix it in 00-brief.md :

• Plan type
• Plan level
• Plan entity
• Plan period
• Applicable region
• Whether formal submission and approval materials are required

Do not write spatial coordination according to a regional plan while also writing departmental tasks according to a special plan without explaining the primary-secondary relationship.

Default settings

• Default plan period:5 year, and clearly state 基期年 / 目标年 / 展望年
• Default research method: supplement public information online, prioritizing original texts from governments, people's congresses, statistics, bulletins, and higher-level plans
• Default main text length:
  • regional：12000-22000 characters
  • specialized：8000-18000 characters
• Default verification rounds:2 rounds; increase to 3 rounds when highly time-sensitive policies, dense indicators, or major project investment calculations are involved
• Default final draft:markdown
• Default output directory:planning-drafts/{slug}-{timestamp}/

If the user explicitly says "no internet access" or "only based on existing materials", the external search may be skipped, but it must be stated in 00-brief.md and the final draft clearly specify the evidence boundary.

Core principles

1. Define the planning attributes first, then write the content. If the planning type, level, legal basis, and approval path are unclear, the longer the main text, the greater the risk.
2. Lower-level plans are subordinate to higher-level plans, and plans of the same type coordinate with each other; development plans are to be followed, and territorial spatial planning provides spatial safeguards.
3. One plan addresses only one object and one main line, and does not mix up "master plan, special plan, implementation plan, and action plan."
4. The planning period, base year, target year, outlook year, and scope of coverage must be clear, and indicators must not drift.
5. Do not write goals without basis, do not force in unverified projects, and do not use formulations without higher-level support.
6. regional The focus is positioning, layout, coordination, and mechanisms;specialized The focus is goals, tasks, projects, and policy tools.
7. Tasks, engineering, projects, policies, mechanisms, and responsible entities must form a closed loop; there cannot be only direction without levers.
8. A project library is not a wish list. Projects must at least explain necessity, maturity, lead entity, and expected contribution.
9. The language should read like planning text, not like an academic paper, investment promotion draft, speech draft, or publicity material.
10. When the user requests a "version ready for approval submission," a working draft close to a formal submission may be generated, but it must not imply that statutory approval procedures have been completed.

Output files

Create a directory for each task:planning-drafts/{slug}-{timestamp}/

• 00-brief.md: task constraints, planning attributes, period, region, whether internet access is enabled
• 01-planning-basis.md: planning basis matrix, higher-level alignment, peer-level alignment, procedural requirements
• 02-terms.md: glossary, unified institution and policy names
• 03-search-plan.md: search questions, keywords, source priority, time boundaries
• 04-source-log.md: source list, URL, publication date, usable key points
• 05-diagnosis.md: development basis, main problems, constraints, benchmarking conclusions
• 06-indicators.md: goal system, indicator table, calculation logic, scope notes
• 07-project-pool.md: major engineering projects, maturity, lead entity, implementation schedule
• 08-outline.md: chapter structure, headings, main line, and chapter tasks
• 09-draft-v1.md: first draft
• 10-review-round-1.md: first-round verification
• 11-draft-v2.md: revised draft
• 12-review-round-2.md: second-round verification
• 13-final.md: final draft
• 14-implementation-matrix.md: task division, annual advancement, and evaluation arrangements

Add as needed:

• 15-compilation-note.md: preparation notes, alignment notes, notes on opinions not adopted
• 16-opinion-log.md: solicitation of opinions and adoption status
• 17-risk-note.md: reminders of matters to be supplemented, such as environmental impact, social stability, legality/fair competition

If the user only wants the result in the chat window, still save the final draft file as usual, and provide the path in the reply.

Layout of main text and attachments

The main text should mainly be written in clearly layered chapters, without pursuing fancy formatting.

Default approach:

• Use ##、### to organize chapters in the main text
• Indicator tables, project tables, and implementation matrices may use Markdown tables
• Do not make large and wide comparison tables unless necessary; for comparative analysis, prefer modular cards
• Keep all table field names stable, and avoid changing scope or names for the same indicator across different files

Workflow

Step 1: Fix the planning attributes, write to 00-brief.md

Prioritize extracting directly from the user conversation; do not repeatedly ask because of default items. At minimum confirm:

• Planning name
• Planning type:regional / specialized
• Planning level: provincial / municipal / district and county / park / cross-regional
• Planning entity and use scenario: formal text / leadership briefing draft / consultation draft / research support draft
• Planning period: base year, target year, outlook year
• Target region and statistical scope
• Whether internet access is mandatory, and whether the latest policies and latest data are required
• Materials the user already has
• Whether supporting deliverables such as a project library, indicator table, and compilation notes are needed

If the planning attributes are ambiguous, first provide 1-2 reasonable type judgments and choose the more prudent one yourself to continue, without stopping at vague discussion.

Step 2: Establish the planning basis matrix, write to 01-planning-basis.md

First read references/planning-rules.md。

At minimum sort out:

• Major deployments of the Party Central Committee and the State Council
• National and provincial higher-level plans
• Development plans at the same level
• Relevant special plans at the same level or higher level
• Territorial spatial planning or spatial control requirements
• Statutory procedure requirements: project initiation, solicitation of opinions, expert demonstration, coordination review, legality/fair competition/environmental impact/risk assessment, etc.

01-planning-basis.md At minimum clearly write:

• Basis for judging planning attributes
• List of higher-level plans
• Objectives, indicators, and major tasks that must be carried forward
• Similar plans or policy boundaries that may conflict
• Statutory procedure matters not yet completed in this draft

Step 3: Unify terminology, write to 02-terms.md

Prioritize unifying:

• Planning names, region names, institution names
• Full names and abbreviations of policy documents
• Industry, sector, public service, and governance terminology
• Indicator names, statistical scope, units

Implementation principles:

• Use the official full name at first occurrence
• Indicator names should use existing formulations from the statistical system or higher-level plans as much as possible
• Do not arbitrarily switch synonyms for the same term
• Colloquial expressions in user materials may be retained as clues, but should not directly enter the final draft

Step 4: Develop a retrieval plan, write to 03-search-plan.md

Retrieval should cover at least five types of questions:

1. Whether the development foundation and real problems actually exist
2. What the higher-level plans, policies, and statutory constraints are
3. What the quantifiable current data and target scope are
4. Which similar regions already have mature practices
5. Whether already issued policies already cover the proposed recommendations, to avoid reinventing concepts

Source priority:

1. Party Central Committee, State Council, ministries and commissions, provincial and municipal governments, people's congress regulations
2. Development and reform, statistics, industry competent departments, public annual reports and bulletins
3. Formal planning texts and policy interpretations
4. Authoritative media and professional institutions
5. Academic research or industry reports

For highly time-sensitive content, prioritize the recent 1-3 years; laws and original planning texts may be moderately relaxed.

Step 5: Collect materials online, write to 04-source-log.md

Collect at least 8 valid sources; for complex tasks strive for 12-20 .

For each source record:

• Title
• Original URL
• Issuing agency
• Release date
• Credibility
• Available key points
• Which chapter it will be used in

Requirements:

• If the original release page can be found, do not use the repost page
• Separate facts, judgments, and inferences
• Old data is only used for historical comparison and does not directly support current conclusions
• Any links, numbers, or cases provided by AI must be verified

Step 6: Conduct basic diagnosis and benchmarking, write into 05-diagnosis.md

05-diagnosis.md It is not a lengthy review, but provides a basis for goals and tasks. At minimum include:

• Development foundation
• Main shortcomings or bottlenecks
• Opportunity windows and external constraints
• Gaps with advanced regions or similar regions
• Judgment on the main line of the plan

Writing requirements:

• Facts first, then judgments
• regional Focus on analyzing spatial structure, node functions, factor flows, and coordination mechanisms
• specialized Focus on analyzing industry foundation, supply-demand contradictions, capability shortcomings, and institutional bottlenecks

Step 7: Design goals, indicators, and project pool, write into 06-indicators.md and 07-project-pool.md

First read references/indicator-and-projects.md。

Indicators must at least clearly state:

• Indicator name
• Indicator attribute:约束性 / 预期性 / 监测性
• Unit
• Base period value
• Target value
• Calculation logic or source standard
• Lead department

The project pool must at least clearly state:

• Project name
• Corresponding task
• Construction or advancement content
• Maturity:谋划 / 前期 / 在建 / 储备
• Implementation schedule
• Lead entity
• Expected results
• Current evidence boundary

Do not force in investment amounts, land scale, or output value pull without basis.

Step 8: Generate structural outline, write into 08-outline.md

Before drafting, read according to the plan type references/structure-templates.md。

Requirements:

• regional The outline must reflect positioning, layout, functional division of labor, coordination tasks, and cross-regional mechanisms
• specialized The outline must reflect overall requirements, development goals, key tasks, major engineering projects, and safeguard measures
• Titles should use standard official document naming, not pursue "viral titles"
• Each chapter should first define "what question this chapter answers," then write the main text

Step 9: Generate first draft, write into 09-draft-v1.md

The first draft should first stabilize the structure and basis, not pursue rhetoric.

Implementation principles:

• Each chapter has a clear function; do not write all-purpose transitional paragraphs
• After goals there must be tasks, after tasks there must be engineering or policy tools, and finally there must be an implementation mechanism
• regional Do not write a cross-regional plan as a division-of-labor checklist for a single administrative region's departments
• specialized Do not have only principled statements without indicator and project support
• For numbers, times, or project statuses that cannot be confirmed, use cautious wording and mark as pending verification

Step 10: Conduct two rounds of verification, write into 10-review-round-1.md and 12-review-round-2.md

Before finalizing, must read references/self-checklist.md。

First round focus:

• Whether the plan attributes and higher-level alignment are valid
• Whether goals, indicators, tasks, and projects form a closed loop
• Whether facts, data, years, and institution names are accurate
• Whether chapter logic is complete

Second round focus:

• Is the language like planning text?
• Does it contain empty talk, clichés, propaganda tone, or academic-paper tone?
• Does it write the vision as a certain commitment?
• Does it omit implementation mechanisms, evaluation mechanisms, or assignment of responsibilities?

When the latest policies, major investments, strongly binding indicators, or sensitive public issues are involved, add a third round of timeliness verification.

Step 11: Form the final draft and implementation matrix, and write them into 13-final.md and 14-implementation-matrix.md

13-final.md are the main texts that the user can directly continue to process.

14-implementation-matrix.md at least includes:

• Key tasks
• Key measures
• Lead unit
• Participating units
• Time nodes
• Corresponding indicators or projects
• Evaluation method

If the user requests supporting materials for review, then supplement:

• 15-compilation-note.md
• 16-opinion-log.md
• 17-risk-note.md

When procedural reminders must be added

If the user requests a “formal approval submission version,” “government issuance version,” or “version that can be directly taken to a meeting,” it must clearly indicate whether the following procedural matters have been completed:

• Inclusion in the project initiation or catalog list
• Solicitation of opinions
• Expert demonstration
• Coordination review
• Legality review
• Fair competition review
• Environmental impact assessment
• Social stability risk assessment

Such matters can be written in 15-compilation-note.md or 17-risk-note.md as “completed / to be completed / not applicable.”

Final draft standards

Only when the following conditions are all met may the final draft be output:

1. The planning type, level, period, and scope are clear
2. It does not conflict with higher-level plans and relevant plans at the same level
3. Goals, indicators, tasks, projects, and mechanisms basically form a closed loop
4. Key facts, policies, years, and institution names can be verified
5. The main text reads like planning text, not like promotional material or an academic paper
6. For uncertain matters, evidentiary boundaries and cautious wording are maintained