From 8ad5e68e396e54ebd2799dc74e014855dea3eb01 Mon Sep 17 00:00:00 2001 From: "promptless[bot]" <179508745+promptless[bot]@users.noreply.github.com> Date: Sat, 6 Dec 2025 00:05:46 +0000 Subject: [PATCH 1/2] Add suggestion quality calibration to pilot guide --- fern/docs/pilot-guide.mdx | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/fern/docs/pilot-guide.mdx b/fern/docs/pilot-guide.mdx index d346396..32a9ab1 100644 --- a/fern/docs/pilot-guide.mdx +++ b/fern/docs/pilot-guide.mdx @@ -117,6 +117,22 @@ Since everyone has different expectations for Promptless, suggestion quality is During your workshop, we'll discuss what "quality" means for your team—technical accuracy, style guide compliance, or catching edge cases. Understanding your quality criteria helps us make Promptless better for you. +#### Understanding Quality Ratings + +To help you calibrate what different quality levels mean for your team: + +**9-10: High Quality, Ready to Publish** +Most suggestions from Promptless are relevant, and typically can be accepted with little to no edits. + +**7-8: Good Quality, Moderate Refinement Needed** +Most suggestions are accurate and relevant, requiring only moderate editing. You're refining style, adding specific details, or adjusting tone rather than rewriting entire sections. Promptless meaningfully reduces your documentation workload. + +**4-6: Some Value, Significant Editing Required** +Suggestions occasionally catch relevant changes and can serve as a starting point, but require significant editing. You're rewriting content, fixing inaccuracies, or filling in missing context. Promptless saves some time, but doesn't dramatically change your workflow. + +**0-3: Creating Negative Value** +Promptless is creating negative value. Most/all suggestions are not good enough to be a useful starting point for doc updates. Even if it's occasionally bringing up things that are relevant, I'd rather start from scratch myself. + ## Documentation Improvement Projects Sometimes teams need foundational work before piloting—like documenting major missing features, completing a large refactor, or creating documentation from scratch. From a3d01caf480d5705326af03f94a7e8ed6c60c671 Mon Sep 17 00:00:00 2001 From: "promptless[bot]" <179508745+promptless[bot]@users.noreply.github.com> Date: Sat, 6 Dec 2025 00:17:58 +0000 Subject: [PATCH 2/2] Sync documentation updates --- fern/docs/pilot-guide.mdx | 15 ++++----------- 1 file changed, 4 insertions(+), 11 deletions(-) diff --git a/fern/docs/pilot-guide.mdx b/fern/docs/pilot-guide.mdx index 32a9ab1..68fe26b 100644 --- a/fern/docs/pilot-guide.mdx +++ b/fern/docs/pilot-guide.mdx @@ -121,17 +121,10 @@ During your workshop, we'll discuss what "quality" means for your team—technic To help you calibrate what different quality levels mean for your team: -**9-10: High Quality, Ready to Publish** -Most suggestions from Promptless are relevant, and typically can be accepted with little to no edits. - -**7-8: Good Quality, Moderate Refinement Needed** -Most suggestions are accurate and relevant, requiring only moderate editing. You're refining style, adding specific details, or adjusting tone rather than rewriting entire sections. Promptless meaningfully reduces your documentation workload. - -**4-6: Some Value, Significant Editing Required** -Suggestions occasionally catch relevant changes and can serve as a starting point, but require significant editing. You're rewriting content, fixing inaccuracies, or filling in missing context. Promptless saves some time, but doesn't dramatically change your workflow. - -**0-3: Creating Negative Value** -Promptless is creating negative value. Most/all suggestions are not good enough to be a useful starting point for doc updates. Even if it's occasionally bringing up things that are relevant, I'd rather start from scratch myself. +* **"9-10":** Most suggestions from Promptless are relevant, and typically can be accepted with little to no edits. +* **"7-8":** Most suggestions are accurate and relevant, requiring only moderate editing. You're refining style, adding specific details, or adjusting tone rather than rewriting entire sections. Promptless meaningfully reduces your documentation workload. +* **"4-6":** Suggestions occasionally catch relevant changes and can serve as a starting point, but require significant editing. You're rewriting content, fixing inaccuracies, or filling in missing context. Promptless saves some time, but doesn't dramatically change your workflow. +* **"0-3":** Promptless is creating negative value. Most/all suggestions are not good enough to be a useful starting point for doc updates. Even if it's occasionally bringing up things that are relevant, I'd rather start from scratch myself. ## Documentation Improvement Projects