InnerVault

technical-whitepaper-writer

Indexedprompts.chat (CC0 prompt collection), akaszhu.ai@gmail.com

# Technical Whitepaper Writer ## Why this skill exists Most AI-generated whitepapers read like marketing documents: vague claims, excessive adjectives, feature lists presented as innovation, unsupported performance…

Open the source (opens github.com) https://github.com/f/prompts.chat

What it is

Prompts from akaszhu.ai@gmail.com.

The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.

The prompt

# Technical Whitepaper Writer

## Why this skill exists

Most AI-generated whitepapers read like marketing documents: vague claims, excessive adjectives, feature lists presented as innovation, unsupported performance numbers, generic architecture diagrams, and roadmaps used as substitutes for technical evidence.

A strong whitepaper instead explains **why a problem exists, what the proposed system does, how it works, why the design is structured that way, what assumptions it makes, how it behaves under normal and failure conditions, and where the design remains limited.**

The goal is a document that reads like **engineering and technical research**, not a sales brochure.

The whitepaper should let a technically capable reader answer:

1. What problem is being solved?
2. Why do existing approaches fail or become insufficient?
3. What is being proposed?
4. How does the proposed system actually work?
5. What are the major components, and how do they interact?
6. What assumptions does the design make?
7. What happens during normal operation?
8. What happens when something goes wrong?
9. What evidence supports the technical claims?
10. What are the limitations and unresolved risks?
11. How is this different from existing approaches?
12. What would someone need to implement, evaluate, or deploy it?

Writing should prioritize **clarity, technical precision, traceability, and intellectual honesty** over impressive-sounding language.

---

## Step 1 — Gather inputs before writing

Do not begin drafting the full whitepaper until the core information is available. If critical information is missing, ask for it (see Step 20) rather than inventing it.

**1. The problem.** State it in one clear sentence, then describe a concrete scenario showing what fails without the proposed solution.

- Avoid: *"The industry needs a revolutionary new approach."*
- Prefer: *"Current systems require each application to independently integrate multiple model providers, resulting in duplicated integration logic, inconsistent observability, and difficult provider switching."*

**2. The project type.** Identify the primary category (and any important secondary categories) without forcing the project into an inappropriate one. Examples: AI/ML system, LLM application, AI infrastructure, data platform, developer tool, cloud/distributed system, cybersecurity system, networking system, database/storage system, hardware/embedded system, robotics system, scientific/research system, enterprise architecture, SaaS platform, API/middleware, agentic system, FinTech, healthcare tech, industrial or energy tech, protocol/standards system, or other.

**3. The core mechanism.** Describe what actually happens inside the system — inputs, processing, state, transformations, decisions, outputs, feedback loops, external dependencies, failure paths, system boundaries. Not a feature list.

- Avoid: *"The platform provides intelligent routing, security, observability, and scalability."*
- Prefer: *"An incoming request is classified according to model, latency, cost, and policy requirements. The routing layer selects an eligible provider, executes the request, records telemetry, and applies retry or fallback logic when the selected provider fails."*

**4. System boundaries.** What's inside the system vs. external? Which components are controlled vs. dependencies? Where does data enter and leave? Where does trust begin and end?

**5. Actors and stakeholders.** Only include actors relevant to the system (e.g., end users, developers, administrators, operators, services, models, agents, data/infrastructure providers, validators, attackers, external systems). For each important actor: what they do, need, control, can observe, and what incentives or constraints shape their behavior.

**6. Resources, economics, or tokens — only when applicable.** If the system has a token, credits, usage units, subscriptions, fees, incentives, rewards, penalties, compute allocation, or quotas, explain their *mechanical* purpose. Never introduce tokenomics or financial mechanisms just because a whitepaper is "expected" to have them. Omit this section if no economic mechanism exists.

**7. Known limitations and risks.** What might fail, degrade, or remain unresolved — scalability limits, latency constraints, dependency risks, model limitations, data quality issues, security assumptions, operational complexity, cost constraints, hardware limitations, privacy concerns, regulatory uncertainty, availability dependencies, integration complexity. State these explicitly; do not hide them.

---

## Step 2 — Choose the whitepaper structure

Do not force every project into an identical template. The default technical spine:

1. Abstract
2. Introduction
3. Problem and Motivation
4. Existing Approaches
5. Design Goals and Non-Goals
6. Proposed Architecture
7. Core Mechanism
8. System Workflow
9. Technical Design
10. Security / Safety / Reliability Model
11. Performance and Scalability
12. Implementation Considerations
13. Worked Example
14. Evaluation / Evidence
15. Limitations and Open Problems
16. Future Work
17. Conclusion
18. References

Not every section is mandatory — use only what materially improves understanding:

- A simple software architecture may skip heavy mathematical analysis.
- An AI research system may need experiments and evaluation methodology.
- A cybersecurity system may need a detailed threat model.
- A hardware system may need physical constraints and benchmarking.
- A distributed system may need consistency, fault tolerance, and failure analysis.
- A commercial SaaS platform may need deployment/operational architecture rather than formal proofs.

---

## Step 3 — Establish the technical delta

If the project builds on or extends existing technology, explicitly trace:

> What existed before → What limitation remained → What this design changes → Why that change matters.

- Avoid: *"This is the world's first revolutionary architecture."*
- Prefer: *"Existing…

Written by the prompts.chat (CC0 prompt collection) community (akaszhu.ai@gmail.com). Not tested by InnerVault.

How to get it

Setup steps: not applicable.

Related

  1. Pitch

    Prompts

    Write mean eye catching pitch

    Indexed prompts.chat (CC0 prompt collection), ballerfx1@gmail.com CC0-1.0

  2. Temitope

    Prompts

    Always act like one fill with wisdom and be extraordinary

    Indexed prompts.chat (CC0 prompt collection), adediwuratemitope9-tech CC0-1.0

  3. Give me note book to learn Spanish with Myanmar translation

    Indexed prompts.chat (CC0 prompt collection), thinn666@gmail.com CC0-1.0

  4. Self-summary

    Prompts

    Give me a summary of what you know about me so far

    Indexed prompts.chat (CC0 prompt collection), monapdx CC0-1.0

  5. subculture

    Prompts

    Explain the cultural significance of ${subculture} and its impact on society.

    Indexed prompts.chat (CC0 prompt collection), etnologiaus2022@gmail.com CC0-1.0

  6. Turns a company's website text into a short list of problems you can see evidence for, what each might cost, and the one fix worth raising first.

    Hand-checked InnerVault (hand-checked), InnerVault Free to use and adapt