…
etc. Must include headings (…). Must be 450-500 words inclusive. Must be plain HTML paragraphs and headings. No placeholders. Must include the e-book promotion paragraph at the end with link. We need to count words. Let’s craft about 470 words. We need to include title line: “Title: …” then blank line then HTML. Title must be SEO-friendly, include “AI” and “ai”. Something like: “AI Automation for Independent Music Teachers: Streamlining Lesson Plans and Progress Tracking”. Ensure includes both uppercase AI and lowercase ai? It says include “AI” and “ai”. Could have both: “AI and ai”. But maybe just include both words somewhere in title. Let’s do: “AI Automation for Independent Music Teachers: How to Automate Lesson Plans with ai”. That includes “AI” and “ai”. Good. Now content: We’ll have headings: maybe H2 for sections: Feeding the System, Building the Pedagogy Prompt, Creating a Repertoire Index, Method Book Deep Dive, Student On-Ramp, Practical Tips, Pitfalls to Avoid, Getting Started. We need to use facts: Book/Page Piano Adventures 2A, p.12; Concepts Introduced: G Major 5-Finger Pattern, Legato Touch, Simple LH Accompaniment (Block Chord); Example Entry: Reinforces: Reading in Treble Clef, Steady Pulse; Title: “Lightly Row”. Also include actionable frameworks: The Pedagogy Prompt, The Repertoire Index Template. Actionable Process: The Method Book Deep Dive, The Student On-Ramp. Also include the tip about focusing on quality over quantity, assign specific goals. Include mantras: list 3-5 short non-negotiable principles. Include batch-process by composer/style. Include practice philosophy. Start with top 50 pieces. Include checklist items: 2-3 core method books analyzed, AI tool configured, current student snapshots. We must embed these facts naturally. Now need to count words. Let’s draft then count. We’ll produce HTML with paragraphs and headings. Word count includes all visible text (including inside tags?). Usually count words in content, not markup. We’ll approximate. Let’s draft: Then blank line. Then HTML:Feeding the System: Input Your Pedagogy, Method Books, and Repertoire
Start by translating your teaching philosophy into clear prompts the AI can follow. Write a “Pedagogy Prompt” that captures core beliefs such as “technique always serves musicality,” “sight‑reading is a weekly ritual,” and “student choice guides 20 % of repertoire.” These statements become the baseline for every generated lesson plan.
Build a Repertoire Index Template
For each piece, record: title, source book/page, concepts introduced, skills reinforced, and a short practice goal. Example from Piano Adventures 2A, p. 12: “Lightly Row” introduces the G Major 5‑Finger Pattern, Legato Touch, and Simple LH Block‑Chord accompaniment while reinforcing reading in treble clef and steady pulse. Tag the entry with those concepts so the AI can retrieve it when a student needs work on legato or accompaniment.
Method Book Deep Dive Process
Select your two‑to‑three core method books. Go through each book page by page, pulling out the concepts and reinforcing skills, then place them in a spreadsheet indexed by concept. This creates a searchable “Skills Tree” that the AI queries to build balanced lesson plans covering technique, theory, and repertoire.
Student On‑Ramp
Create snapshot profiles for your five most typical students: current level, strengths, weaknesses, practice habits, and goals. When you add a new student, the AI can clone the closest snapshot and adjust the plan based on the Pedagogy Prompt and Repertoire Index.
Actionable Tips for Efficient Implementation
Begin with your top 50 most‑assigned pieces rather than trying to catalogue hundreds at once. Focus on quality over quantity: assign specific, measurable goals (e.g., “left hand alone, mm = 60”). Batch‑process by composer or style—duplicate a base template for all your Bach Anna Magdalena Notebook pieces and modify only the unique details.
Practice Philosophy and Pitfalls to Avoid
Define clear expectations for home practice. The AI should frame instructions as “practice hands separately until each is secure at mm = 60, then combine slowly,” reinforcing that technique serves musicality. Avoid generated plans that skip warm‑up, lack a clear goal, or assign repertoire far beyond the student’s current reading level.
Teaching Mantras (Non‑Negotiable Principles)
1. Technique always serves musicality.
2. Sight‑reading is a weekly ritual.
3. Student choice guides 20 % of repertoire.
4. Mastery is measured by steady pulse and accurate articulation.
5. Feedback is immediate and specific.
Getting Started Checklist
☐ Analyze 2‑3 core method books and tag contents to your Skills Tree.
☐ Configure your AI tool with the Pedagogy Prompt and Method Book data.
☐ Update current student snapshots for your five most typical students.
☐ Build the Repertoire Index using the template, starting with the top 50 pieces.
☐ Run a test lesson plan for a sample student and refine the prompts.
For a comprehensive guide with detailed workflows, templates, and additional strategies, see my e-book: AI for Independent Music Teachers: How to Automate Lesson Plan Creation and Student Progress Tracking.
Now count words. Need to count visible words (text inside tags). Let’s copy text and count manually. I’ll extract paragraphs: Title line not counted? Probably title line is separate; but we need total words 450-500 for article content. Usually title not counted? Safer to count everything after title line? The instruction: “Write a concise 450-500 word WordPress blog post in HTML format”. Likely the article content (including headings, paragraphs) should be 450-500 words. Title line maybe not counted but safer to include in count? We’ll aim for ~470 words in the HTML body (excluding title line). Let’s count. I’ll write out the content (excluding the title line) and count. Content: Feeding the System: Input Your Pedagogy, Method Books, and Repertoire Start by translating your teaching philosophy into clear prompts the AI can follow. Write a “Pedagogy Prompt” that captures core beliefs such as “technique always serves musicality,” “sight‑reading is a weekly ritual,” and “student choice guides 20 % of repertoire.” These statements become the baseline for every generated lesson plan. Build a Repertoire Index Template For each piece, record: title, source book/page, concepts introduced, skills reinforced, and a short practice goal. Example from Piano Adventures 2A, p. 12: “Lightly Row” introduces the G Major 5‑Finger Pattern, Legato Touch, and Simple LH Block‑Chord accompaniment while reinforcing reading in treble clef and steady pulse. Tag the entry with those concepts so the AI can retrieve it when a student needs work on legato or accompaniment. Method Book Deep Dive Process Select your two‑to‑three core method books. Go through each book page by page, pulling out the concepts and reinforcing skills, then place them in a spreadsheet indexed by concept. This creates a searchable “Skills Tree” that the AI queries to build balanced lesson plans covering technique, theory, and repertoire. Student On‑Ramp Create snapshot profiles for your five most typical students: current level, strengths, weaknesses, practice habits, and goals. When you add a new student, the AI can clone the closest snapshot and adjust the plan based on the Pedagogy Prompt and Repertoire Index. Actionable Tips for Efficient Implementation Begin with your top 50 most‑assigned pieces rather than trying to catalogue hundreds at once. Focus on quality over quantity: assign specific, measurable goals (e.g., “left hand alone, mm = 60”). Batch‑process by composer or style—duplicate a base template for all your Bach Anna Magdalena Notebook pieces and modify only the unique details. Practice Philosophy and Pitfalls to Avoid Define clear expectations for home practice. The AI should frame instructions as “practice hands separately until each is secure at mm = 60, then combine slowly,” reinforcing that technique serves musicality. Avoid generated plans that skip warm‑up, lack a clear goal, or assign repertoire far beyond the student’s current reading level. Teaching Mantras (Non‑Negotiable Principles) 1. Technique always serves musicality. 2. Sight‑reading is a weekly ritual. 3. Student choice guides 20 % of repertoire. 4. Mastery is measured by steady pulse and accurate articulation. 5. Feedback is immediate and specific. Getting Started Checklist ☐ Analyze 2‑3 core method books and tag contents to your Skills Tree. ☐ Configure your AI tool with the Pedagogy Prompt and Method Book data. ☐ Update current student snapshots for your five most typical students. ☐ Build the Repertoire Index using the template, starting with the top 50 pieces. ☐ Run a test lesson plan for a sample student and refine the prompts. For a comprehensive guide with detailed workflows, templates, and additional strategies, see my e-book: AI for Independent Music Teachers: How to Automate Lesson Plan Creation and Student Progress Tracking. Now count words. I’ll count each sentence’s words. I’ll write each line with word count. Line1: “Feeding the System: Input Your Pedagogy, Method Books, and Repertoire” Words: Feeding(1) the2 System:3 Input4 Your5 Pedagogy,6 Method7 Books,8 and9 Repertoire10 => 10 Paragraph1: “Start by translating your teaching philosophy into clear prompts the AI can follow. Write a “Pedagogy Prompt” that captures core beliefs such as “technique always serves musicality,” “sight‑reading is a weekly ritual,” and “student choice guides 20 % of repertoire.” These statements become the baseline for every generated lesson plan.” Count: Start1 by2 translating3 your4 teaching5 philosophy6 into7 clear8 prompts9 the10 AI11 can12 follow13. Write14 a15 “Pedagogy16 Prompt”17 that18 captures19 core20 beliefs21 such22 as23 “technique24 always25 serves26 musicality,”27 “sight‑reading28 is29 a30 weekly31 ritual,”32 and33 “student34 choice35 guides36 20 %37 of38 repertoire.”39 These40 statements41 become42 the43 baseline44 for45 every46 generated47 lesson48 plan