subagent-instruction-operationalization

Converts style specification analyses into structured LLM subagent prompts that replicate a target writing voice.

13|2|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/aaddrick/written-voice-replication --skill subagent-instruction-operationalization-aaddrick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-instruction-operationalization
Source: https://github.com/aaddrick/written-voice-replication/tree/main/.claude/skills/subagent-instruction-operationalization
Command: npx skills add https://github.com/aaddrick/written-voice-replication --skill subagent-instruction-operationalization-aaddrick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Analytical style reports describe what a voice is but not how to reproduce it. This Skill bridges that gap by translating psycholinguistic and stylometric analysis outputs (LIWC, Big Five, MDPI archetype, readability, speech acts) into a concrete, testable LLM subagent prompt with measurable constraints and verification criteria. ## Core Features & Use Cases - Constraint Translation: Converts nine analysis dimensions (readability, stylometric fingerprint, emotional valence, rhetorical structure, speech acts, and more) into prompt directives ranked by enforcement strength. - Few-Shot Example Selection: Guides selection of 3-5 representative corpus samples to anchor style constraints, the strongest enforcement mechanism. - Testing and Validation: Includes pass/fail criteria for FK grade, sentence length, sentiment, and function-word rates, plus a token budget and self-verification section. - Use Case: After running upstream writing-style analyses on a Reddit corpus, use this Skill to assemble a versioned persona prompt that generates text matching the author's voice, then validate it against the source material. ## Quick Start Use the subagent-instruction-operationalization skill to convert the completed style specification in docs/analysis into a voice-replication subagent prompt.

Frequently Asked Questions about subagent-instruction-operationalization

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a writing style analysis into an LLM prompt?

Inventory the completed analysis dimensions, select 3-5 typical few-shot examples from the corpus, then translate each dimension into prompt sections ordered by enforcement strength: role frame, complexity targets, syntactic fingerprint, emotional valence, and rhetorical structure. Finish with self-verification instructions and test against source material.

What makes a voice replication prompt effective?

Few-shot examples are the strongest constraint, followed by measurable numerical targets like Flesch-Kincaid grade and sentence length ranges. Distributional constraints such as speech act ratios are weakly enforceable through instructions alone and rely primarily on examples.

How many analysis dimensions are needed before generating a voice prompt?

Seven or more of the nine dimensions supports a full prompt. Four to six yields a partial prompt with documented gaps. One to three produces only targeted constraints, and zero dimensions means the upstream analyses must be run first.

How do I test whether a generated voice prompt actually works?

Generate text on three different topics, then measure FK grade, sentence length, sentiment compound, and function-word rates against the source fingerprint. Passing means FK within plus or minus 1 grade, sentence length within 3 words, and sentiment within 0.15 of target.

What are the limitations of instruction-based style transfer?

Lexical and complexity constraints are strongly enforceable, but structural patterns drift and distributional targets like speech act ratios are only weakly enforceable without few-shot examples. One-shot style transfer accuracy ranges from roughly 67.6% to 94.7% depending on prompting strategy.

When should I not use subagent instruction operationalization?

Do not use it when no style specification exists yet, when the goal is impersonation for deception or harassment, or when the target is a generic professional tone. Simple role prompts suffice for generic styles without specification-driven constraints.