Prompts for building with better business context.
Use these templates inside your own Groundwork system to ask better questions, keep the source of truth healthy, call the right advisors, and build new workflows around your business context.
How to use this
Use these prompts as examples, then shape them around your business.
Copy a prompt, paste it into the AI chat connected to your Groundwork folder, and replace the bracketed details with your own context. These templates show what you can do with your source of truth, but you stay in control: adapt the prompts, change the structure, teach advisors new material, decide what gets saved, and keep Groundwork aligned with how your business actually works.
Replace bracketed text like [decision], [new information], or [paste learning material] with your own details. If Groundwork does not know something yet, ask it to add the gap to the Question Library instead of guessing.
Browse prompt sections
Start Here
Start by making the source of truth more useful.
Use these prompts when you want Groundwork to tell you what it needs next, what information is missing, which gaps matter most, and how to turn your source of truth into a stronger business system.
Import attached files into Groundwork
Turn documents, notes, exports, or research files into source updates.
Prompt template
"Save the uploaded files into the file section of Groundwork. Then use the uploaded files to update my Groundwork source of truth. Review every file first, identify confirmed business facts, useful evidence, assumptions, conflicts, stale information, and missing context. Then update the relevant Groundwork source records, Question Library, advisor knowledge only where appropriate, local website viewer pages, source health, change log, and sync log. Do not invent details. Add anything unresolved as an open question with the source file it came from."
Ask Groundwork what it needs
Find the most useful next source-of-truth improvements.
Prompt template
"Review my current Groundwork source of truth and tell me what information would make it more useful. Prioritize the missing, unclear, outdated, or weakly supported information that would most improve advisor recommendations, decisions, planning, and business clarity."
Create a priority one-sheet
Turn source gaps into a simple action sheet.
Prompt template
"Create a one-page priority sheet for improving my Groundwork source of truth. Include the top priority gaps, why each one matters, what answer or data is needed, which business area it improves, which advisor benefits, and the suggested prompt I should use to fill it in."
Show missing data by business area
See exactly where the source of truth is thin.
Prompt template
"Show me what data is missing by business area: strategy, customers, offers, product, sales, marketing, finance, operations, technology, risks, decisions, assumptions, metrics, and initiatives. For each area, list missing facts, weak assumptions, stale records, and the highest-value next question."
Rank source-of-truth priorities
Choose which gaps to fill first.
Prompt template
"Rank the top source-of-truth improvements by business value. Score each one based on how much it would improve focus, advisor quality, decision-making, risk reduction, revenue clarity, customer understanding, and execution. Give me the top 10 in priority order."
Generate a completion plan
Create a practical plan for making Groundwork more complete.
Prompt template
"Create a practical source-of-truth completion plan for the next 30 days. Group the work by week, include the questions I should answer, the source material I should gather, the business areas affected, and what Groundwork should update after each answer."
Ask the advisors what they need
Use advisor perspectives to identify better context.
Prompt template
"Ask every active Groundwork advisor what information they need to give better recommendations. Combine their answers into a prioritized list of missing facts, useful source materials, important questions, and business areas that need better evidence."
Turn notes into useful source updates
Convert raw notes into structured Groundwork improvements.
Prompt template
"Review these notes and tell me how they could improve my Groundwork source of truth: [paste notes]. Identify confirmed facts, assumptions, open questions, conflicts, source updates needed, advisor knowledge opportunities, and website viewer updates."
Find stale or low-confidence records
Improve trust in the current source of truth.
Prompt template
"Find stale, low-confidence, unsupported, or conflicting records in my Groundwork source of truth. Create a priority list showing what should be confirmed, corrected, marked outdated, moved to the review queue, or turned into open questions."
Simple Prompts
Simple prompts for everyday Groundwork use.
Use these when you want Groundwork to answer questions, summarize business context, update facts, or point you toward the next useful decision.
Show me what matters now
Start a focused business review without changing the system.
Prompt template
"Using the current Groundwork source of truth, show me the most important goals, active priorities, unresolved risks, and open questions I should pay attention to this week."
Find missing context
Turn uncertainty into a clear completion list.
Prompt template
"Review the current source of truth and tell me what important business information is missing, unclear, outdated, or unsupported by evidence. Add useful gaps to the Question Library."
Ask the best next questions
Get a short set of useful questions instead of a long intake.
Prompt template
"Ask me the five questions that would most improve my Groundwork system right now. Prioritize questions that would improve advisor recommendations, priorities, decisions, or operating clarity."
Summarize the business for AI
Prepare context for another AI conversation.
Prompt template
"Create a concise AI briefing from my Groundwork source of truth. Include goals, customers, offers, current priorities, constraints, recent decisions, open questions, and what the AI should not assume."
Review a decision
Compare a decision against what Groundwork already knows.
Prompt template
"Evaluate this decision against my goals, current priorities, customers, offers, operations, finances, risks, assumptions, and recent decisions: [decision]. Tell me the tradeoffs and what source updates are needed."
Update the source of truth
Add a new fact while keeping Groundwork synchronized.
Prompt template
"Update the Groundwork source of truth with this new information: [new information]. Update any affected business areas, related questions, advisors, change log, and local website pages."
Questions
Prompts that ask better questions.
These prompts help a user discover what Groundwork knows, what it does not know yet, and which answers would make the system more useful.
Business basics
Clarify the basic identity of the business.
Prompt template
"What basic business details are missing from Groundwork, including who we serve, what we sell, where we operate, how we describe the company, and what should be treated as unknown?"
Customer clarity
Improve customer and market context.
Prompt template
"What do we currently know about our best customers, their buying triggers, objections, alternatives, and desired outcomes? What customer questions should I answer next?"
Offer strength
Review products, services, packages, and pricing.
Prompt template
"Which offers look strongest based on the current source of truth, and what information is missing about pricing, margins, delivery effort, objections, or customer fit?"
Priority check
Separate active priorities from old work.
Prompt template
"Which priorities appear active, which appear stale, and which should be moved to the review queue or archive based on the current Groundwork records?"
Assumption check
Find unconfirmed beliefs that affect planning.
Prompt template
"Which assumptions are still unconfirmed, which decisions depend on them, and what evidence would help validate or reject them?"
Advisor handoff
Get multiple perspectives on the same issue.
Prompt template
"Have the Strategy, Finance, Marketing, Product, Operations, AI, People, and Risk Advisors review this issue from their own perspectives while staying grounded in the source of truth: [issue]."
Evidence check
Separate facts from unsupported claims.
Prompt template
"Review this business claim against the Evidence Library and source records: [claim]. Mark what is confirmed, assumed, outdated, conflicting, or missing."
Outcome check
Tie work back to goals and measures.
Prompt template
"Which current projects, initiatives, or planned work are most directly connected to our goals and measurable outcomes? Which ones have unclear business value?"
Risk scan
Find risks that should not be ignored.
Prompt template
"Review Groundwork for operational, financial, product, customer, technology, AI, people, and execution risks. Which risks need decisions, owners, evidence, or mitigation plans?"
Maintenance
Prompts for keeping Groundwork accurate and optimized.
Use these to keep the source of truth complete, the viewer synchronized, advisor knowledge separated, and system changes reviewed before they affect the structure.
Review source health
Check completeness, freshness, evidence, and consistency.
Prompt template
"Review source health across Groundwork. Check completeness, outdated records, missing evidence, conflicts, unanswered questions, review dates, stale priorities, advisor knowledge freshness, and website sync status."
Rebuild the viewer
Update the local website from the latest source records.
Prompt template
"Rebuild the Groundwork website from the latest source of truth. Create the required backup first, then update affected pages, source health, question library, advisor pages, change log, and sync log."
Backup the system
Create a recoverable copy before important work.
Prompt template
"Backup Groundwork now. Create a timestamped zip backup of the complete system folder, log the backup, and update source health with the latest backup status."
Clean stale context
Keep the source of truth from drifting.
Prompt template
"Find stale, duplicate, outdated, weakly supported, or conflicting business context. Do not delete it silently. Recommend what should be updated, marked outdated, archived, or turned into an open question."
Monthly business review
Run a full advisor review.
Prompt template
"Run the monthly business review. Have all active advisors review their domains, create dated outputs, summarize the top issues, opportunities, risks, evidence gaps, recommended decisions, and source updates."
Advisor knowledge update
Teach the right advisors without mixing their knowledge banks.
Prompt template
"Update advisor knowledge with this material: [paste learning material]. Review it across every active advisor and add it only to advisor knowledge banks where it is useful. Update related skills, question banks, indexes, logs, and advisor pages."
Question Library cleanup
Keep completed and open questions accurate.
Prompt template
"Review the Question Library. Make sure completed questions are still visible, open questions are useful, deferred questions are intentional, not-applicable questions are labeled clearly, and suggested prompts are still helpful."
System impact review
Check risky changes before changing Groundwork behavior.
Prompt template
"Perform a System Impact Review for this requested change before applying it: [change]. Explain what could affect source integrity, website sync, advisor behavior, local-only operation, privacy, navigation, file structure, or governance rules."
Apply a system updater
Safely install a Groundwork improvement file.
Prompt template
"Apply this System Updater Markdown file: [paste or reference updater]. Review it completely, perform a System Impact Review, create the required backup, apply the update, preserve conflicts, update affected manuals and website pages, and log what changed."
Advisors
Advisor prompts for specialized business review.
Groundwork includes role-based advisors. These prompts call the right advisor perspective while keeping recommendations grounded in the same source of truth.
Strategy Advisor review
Pressure-test direction, focus, and tradeoffs.
Prompt template
"Ask the Strategy Advisor to review the current goals, positioning, active priorities, decisions, risks, and assumptions. What should we focus on, stop doing, decide, or learn next?"
Product Advisor review
Improve roadmap and product direction.
Prompt template
"Ask the Product Advisor to review roadmap priorities, customer feedback, product-market fit signals, feature requests, packaging, and open product questions. What should move forward, wait, or be validated first?"
Finance Advisor review
Review profitability, pricing, and financial clarity.
Prompt template
"Ask the Finance Advisor to review pricing, margins, costs, revenue quality, cash constraints, and missing financial facts. Which decisions need better financial evidence?"
Marketing Advisor review
Improve messaging and campaign direction.
Prompt template
"Ask the Marketing Advisor to review positioning, audience clarity, customer language, proof, content themes, campaigns, channels, and missing facts that would improve marketing decisions."
Sales Advisor review
Review pipeline, objections, offers, and sales process.
Prompt template
"Ask the Sales Advisor to review offers, buying objections, sales stages, follow-up gaps, conversion risks, and the evidence we have about why customers say yes or no."
Operations Advisor review
Find workflow, handoff, and execution issues.
Prompt template
"Ask the Operations Advisor to review active workflows, recurring bottlenecks, responsibilities, handoffs, tools, manual work, and process gaps that should be clarified or improved."
Technology Advisor review
Check tools, systems, security, and maintainability.
Prompt template
"Ask the Technology Advisor to review current tools, systems, integrations, security concerns, data flows, technical risks, and software improvements that would support the business."
AI Advisor review
Identify practical AI use cases.
Prompt template
"Ask the AI Advisor to identify the best business processes to improve with AI. Prioritize practical workflows with clear owners, repeatable inputs, quality checks, and business value."
People Advisor review
Clarify roles, accountability, and capacity.
Prompt template
"Ask the People Advisor to review role clarity, decision ownership, capacity constraints, hiring needs, training gaps, and people-related risks without creating a separate team source file."
Risk Advisor review
Find risks and mitigation needs.
Prompt template
"Ask the Risk Advisor to review the current source of truth for financial, customer, operational, legal, security, AI, people, and execution risks. Which risks need action or better evidence?"
Teach advisors from a book
Turn useful ideas from a book into advisor knowledge.
Prompt template
"Teach the advisors from these book notes: [paste your notes, key ideas, or short excerpts]. Review the material across every active advisor, add useful ideas to the right advisor knowledge banks, create any repeatable skills or diagnostic questions, and keep it separate from confirmed business facts unless it directly describes my business."
Teach advisors from a website
Use an article, web page, or online guide to improve advisor thinking.
Prompt template
"Review this website or article for advisor knowledge: [link or pasted notes]. Identify which advisors should learn from it, summarize the useful principles in plain language, add them to the right advisor knowledge banks, and note any source limits, assumptions, or follow-up questions."
Teach one advisor
Add targeted learning material to a specific advisor.
Prompt template
"Add this learning material to the [Advisor Name] Advisor: [paste notes, book ideas, article summary, framework, or training material]. Update that advisor's knowledge bank, skills, question bank, and advisor page if useful. Do not add it to other advisors unless it clearly helps them too."
Turn material into advisor skills
Convert outside learning into repeatable advisor behavior.
Prompt template
"Turn this learning material into reusable advisor skills: [paste material or notes]. For each useful skill, name the advisor it belongs to, explain when the advisor should use it, add any diagnostic questions, and update the related advisor knowledge without overwriting source-of-truth business records."
Outputs
Prompts for creating useful business outputs.
Use these to turn your Groundwork source of truth into summaries, outlines, emails, agendas, reports, memos, and other working materials that show how flexible the system can be.
Formatted business summary
Create a polished summary from the current source of truth.
Prompt template
"Create a formatted business summary from my Groundwork source of truth. Include what the business does, who it serves, current goals, top priorities, key offers, active risks, recent decisions, open questions, and a short next-step section. Clearly label anything that is unknown or unsupported."
Executive one-page brief
Turn Groundwork context into a concise leadership brief.
Prompt template
"Create a one-page executive brief using the current Groundwork source of truth. Use clear headings, short bullets, and a decision-ready format. Include the situation, goals, current priorities, constraints, key risks, recommended decisions, and missing information."
Presentation outline
Generate a deck structure for a meeting, pitch, or internal review.
Prompt template
"Create a presentation outline for [audience or meeting purpose] using my Groundwork source of truth. Include slide titles, the key message for each slide, supporting points, suggested visuals, and any source gaps that should be answered before presenting."
Customer email draft
Draft an email grounded in offers, audience, and customer context.
Prompt template
"Draft a customer email for [purpose] using my Groundwork source of truth. Match the audience, offer, positioning, tone, objections, and call to action already captured in Groundwork. Do not invent claims, proof, pricing, or guarantees."
Internal update email
Summarize priorities, changes, and next steps for a team or stakeholder.
Prompt template
"Create an internal update email from the current Groundwork source of truth. Summarize what changed, current priorities, decisions made, blockers, upcoming work, open questions, and what each stakeholder needs to know or do next."
Meeting agenda
Create a focused meeting plan from current priorities and open questions.
Prompt template
"Create a meeting agenda for [meeting topic] using Groundwork. Include the meeting goal, decisions needed, discussion topics, relevant context, open questions, pre-read notes, and follow-up items to update in the source of truth afterward."
Decision memo
Turn a decision into a structured memo with tradeoffs.
Prompt template
"Create a decision memo for this decision: [decision]. Use Groundwork to summarize the context, options, goals affected, customer impact, financial impact, operational impact, risks, assumptions, recommendation, open questions, and source updates needed after the decision."
Weekly status report
Generate a practical status update from goals and active work.
Prompt template
"Create a weekly status report from my Groundwork source of truth. Include wins, active priorities, project status, risks, decisions needed, metrics to watch, stale items, and the highest-value source-of-truth updates to make next."
Offer or sales sheet draft
Turn offer context into a usable sales asset.
Prompt template
"Create a draft offer sheet for [offer name] using Groundwork. Include the target customer, problem, outcome, what is included, why it matters, proof we have, pricing if confirmed, common objections, call to action, and missing details that should not be guessed."
Social post batch
Generate content ideas from grounded business context.
Prompt template
"Create a batch of social media post drafts from my Groundwork source of truth for [campaign, audience, or offer]. Include channel, draft copy, core message, call to action, source context used, and any claims that need proof before publishing."
Client or stakeholder FAQ
Create helpful Q&A material from known business context.
Prompt template
"Create a practical FAQ for [audience or topic] using Groundwork. Answer only from confirmed source-of-truth context, label unknowns, include suggested follow-up questions, and note which answers may need advisor review before sharing."
Action plan
Turn an advisory review into concrete next steps.
Prompt template
"Create an action plan from the current Groundwork source of truth for [goal or issue]. Include recommended actions, owners if known, priority, expected outcome, dependencies, risks, review dates, and source-of-truth updates needed as work progresses."
Build ideas
Smaller build prompts for extending a Groundwork system.
Use these when a user wants to add a focused workflow or section to their own Groundwork system without weakening the source-of-truth rules.
Add a new business area
Create a focused section without turning Groundwork into one big page.
Prompt template
"Build a new Groundwork business area for [business area]. Use existing Groundwork patterns. Add canonical source records first, add useful questions to the Question Library, update related advisors, create or update the matching viewer page, update navigation cards only where appropriate, and log the change."
Create a review queue workflow
Track decisions, assumptions, stale records, and advisor recommendations.
Prompt template
"Build or improve the Review Queue. It should show decisions due for review, assumptions needing validation, stale records, conflicts, weak domains, high-priority questions, and advisor recommendations awaiting a user decision. Keep the source of truth canonical and update the viewer after source updates."
Create an evidence library workflow
Track where facts came from and how reliable they are.
Prompt template
"Build or improve the Evidence Library. Track source materials, source freshness, trust level, sensitivity notes, related source records, questions answered, conflicts, and whether each source is still useful. Do not turn the page into a raw document dump."
Create a metrics review system
Keep goals tied to numbers and review dates.
Prompt template
"Build a metrics review system inside Groundwork. Track key metrics, definitions, source, owner, cadence, current value, target value, confidence, last updated date, review date, related goals, and open questions. Update source health and advisor guidance."
Create an offer review system
Review services, packages, products, and pricing.
Prompt template
"Build an offer review system inside Groundwork. Track each offer, target customer, promise, price, margin, delivery effort, objections, proof, risks, open questions, and review date. Have Marketing, Sales, Finance, Product, Operations, and Risk Advisors review the structure."
Create an SOP library
Document repeatable work without losing business context.
Prompt template
"Build a lightweight SOP library inside Groundwork for repeatable business processes. Track purpose, owner, trigger, inputs, steps, outputs, quality checks, tools used, risks, update date, review date, and related questions. Keep operational facts in the source of truth and rebuild the viewer."
Create an AI workflow registry
Track AI use cases, owners, prompts, and quality controls.
Prompt template
"Build an AI workflow registry inside Groundwork. Track candidate AI workflows, business value, owner, input data, prompt or instruction location, review process, output quality checks, risks, privacy notes, status, and next action. Have the AI, Operations, Technology, People, and Risk Advisors review it."
Full build prompts
Detailed prompts for building new Groundwork systems.
These are longer templates for adding complete workflows to an existing Groundwork folder while preserving the source-of-truth rules, advisor model, Question Library, local website, backups, and logs.
Build prompt
Full Product Backlog System
A detailed build prompt for adding backlog capture, prioritization, advisor review, review queue behavior, and shipped/rejected history to a Groundwork system.Open full prompt
Build a full Product Backlog system inside my Groundwork system.
Goal:
Create a practical product backlog that helps me capture, prioritize, review, and track product ideas, feature requests, bugs, improvements, experiments, customer needs, and roadmap candidates while keeping Groundwork's source of truth accurate.
Current Groundwork system rules:
- Start by inspecting the current Groundwork folder, source files, website pages, advisor files, logs, manuals, navigation hubs, and current state of the system.
- Fit this feature into the existing Groundwork layout, naming, card patterns, advisor patterns, source structure, Question Library, Review Queue, Source Health, Change Log, and local website viewer.
- Do not take over, replace, rebrand, redesign, or reorganize the whole system. Add this feature as an extension of whatever currently exists.
- If a similar feature, page, source file, advisor workflow, or question set already exists, improve or extend it instead of creating a duplicate.
- Keep the canonical source of truth in /src/source. Update source records first, then update the local website viewer.
- Treat website pages as viewer pages only, not as the business source of truth.
- Unknown, missing, ambiguous, or unsupported information becomes Question Library items. Do not invent business facts.
- Preserve completed questions and label every question clearly as Open, Completed, Deferred, or Not Applicable.
- Keep advisor knowledge separated by advisor. Do not merge advisor knowledge banks.
- Do not add remote services, analytics, cloud dependencies, package managers, scripts, servers, databases, or tracking.
- Reuse existing Groundwork visual layout and navigation patterns. Add page cards only in the appropriate existing section or tool hub; do not add unnecessary top-level navigation.
- If the request could affect source integrity, website sync, advisor behavior, local-only operation, privacy, navigation, file structure, or governance rules, perform a System Impact Review before changing the system.
- Create the required backup before major structural changes when the current Groundwork system calls for it.
- Log meaningful changes in the existing Groundwork logs.
- If you are unsure how this should fit the current system, what page or source file should own it, or which behavior the user wants, ask concise clarifying questions before building. Ask only what is needed to avoid a bad assumption.
System to create:
1. Product Backlog source structure
Track each backlog item with:
- Title
- Type: feature, bug, improvement, experiment, research, technical debt, customer request, content, operational improvement, or other
- Status: idea, needs review, accepted, planned, in progress, blocked, shipped, rejected, archived, or deferred
- Priority: critical, high, medium, low, or later
- Customer or stakeholder source
- Problem being solved
- Desired outcome
- Evidence or source material
- Related goals
- Related customer segments
- Related offers, products, or services
- Estimated effort if known
- Expected impact if known
- Risks and dependencies
- Open questions
- Decision history
- Owner if known
- Target timeframe if known
- Created date
- Last updated date
- Review date
- Confidence level
- Related source records
- Related advisor recommendations
- Reason rejected, deferred, or archived when applicable
- Outcome notes after shipment
2. Backlog views
Add viewer content that helps me see:
- Priority backlog items
- Items needing review
- Blocked items
- Planned work
- Recently shipped items
- Rejected or archived items
- Items grouped by product area, customer need, status, and priority
- Items with weak evidence
- Items with unresolved questions
- Items due for review
- Items linked to current goals and initiatives
- Items that may duplicate existing work
3. Product Advisor workflow
Update the Product Advisor so it can:
- Review backlog quality
- Identify missing evidence
- Compare backlog items against goals, customer needs, product direction, and business constraints
- Recommend what to validate before building
- Identify roadmap conflicts
- Suggest which backlog items should be split, merged, rejected, or clarified
- Flag items that are not supported by customer evidence or business goals
4. Cross-advisor review
Have these advisors review the backlog system:
- Strategy Advisor: strategic fit and focus
- Product Advisor: backlog quality and roadmap logic
- Sales Advisor: customer demand and sales feedback
- Marketing Advisor: positioning and messaging implications
- Operations Advisor: delivery complexity and process impact
- Technology Advisor: implementation risk and maintainability
- Finance Advisor: margin, cost, and return expectations
- Risk Advisor: delivery, legal, data, and customer risks
5. Question Library
Add useful questions such as:
- Which customer problem does this backlog item solve?
- What evidence supports this request?
- Who asked for it and how often has it come up?
- What goal does this support?
- What happens if we do not build it?
- What is the smallest useful version?
- What needs to be true before we commit?
- What risk or dependency could block it?
6. Suggested prompts
Add prompts I can use later, including:
- Add this backlog item: [details].
- Review the backlog and show me the top items needing a decision.
- Ask the Product Advisor to prioritize the backlog against current goals and customer evidence.
- Turn this customer feedback into backlog items and open questions.
- Move this item to planned work and update related goals, decisions, and review dates.
- Mark this item shipped and update the change log, related metrics, and advisor notes.
7. Maintenance behavior
Make sure the backlog can be reviewed over time:
- Stale items should appear in the Review Queue.
- Shipped items should remain visible as history.
- Rejected items should keep the reason they were rejected.
- Backlog decisions should be logged.
- Weak evidence should create open questions.
- Changes should update the local website viewer.
- Backlog items should not silently disappear when priorities change.
- Items should be linked to decisions, assumptions, metrics, initiatives, customer research, and review queue records when those exist.
Before building:
- Inspect the existing Product, Initiatives, Decisions, Assumptions, Metrics, Customer, Review Queue, Evidence, and Advisor areas.
- Decide whether the backlog should extend an existing Product or Initiatives page or needs a new focused page.
- If you are unsure, ask clarifying questions before building.
- Then add the smallest useful backlog system that fits the current Groundwork status and can grow over time.
Build prompt
Social Media Planning and Tracking System
A detailed build prompt for planning posts, tracking status, reviewing campaign context, connecting posts to business goals, and recording performance lessons.Open full prompt
Build a full Social Media Planning and Tracking system inside my Groundwork system.
Goal:
Create a practical system for planning, scheduling, tracking, reviewing, and improving social media posts while keeping posts connected to business goals, offers, campaigns, customer insights, channels, content themes, approvals, and performance.
Current Groundwork system rules:
- Start by inspecting the current Groundwork folder, source files, website pages, advisor files, logs, manuals, navigation hubs, and current state of the system.
- Fit this feature into the existing Groundwork layout, naming, card patterns, advisor patterns, source structure, Question Library, Review Queue, Source Health, Change Log, and local website viewer.
- Do not take over, replace, rebrand, redesign, or reorganize the whole system. Add this feature as an extension of whatever currently exists.
- If a similar feature, page, source file, advisor workflow, or question set already exists, improve or extend it instead of creating a duplicate.
- Keep the canonical source of truth in /src/source. Update source records first, then update the local website viewer.
- Treat website pages as viewer pages only, not as the business source of truth.
- Unknown, missing, ambiguous, or unsupported information becomes Question Library items. Do not invent business facts.
- Preserve completed questions and label every question clearly as Open, Completed, Deferred, or Not Applicable.
- Keep advisor knowledge separated by advisor. Do not merge advisor knowledge banks.
- Do not add remote services, analytics, cloud dependencies, package managers, scripts, servers, databases, or tracking.
- Reuse existing Groundwork visual layout and navigation patterns. Add page cards only in the appropriate existing section or tool hub; do not add unnecessary top-level navigation.
- If the request could affect source integrity, website sync, advisor behavior, local-only operation, privacy, navigation, file structure, or governance rules, perform a System Impact Review before changing the system.
- Create the required backup before major structural changes when the current Groundwork system calls for it.
- Log meaningful changes in the existing Groundwork logs.
- If you are unsure how this should fit the current system, what page or source file should own it, or which behavior the user wants, ask concise clarifying questions before building. Ask only what is needed to avoid a bad assumption.
System to create:
1. Social media source structure
Track each social media post with:
- Working title
- Channel or platform
- Status: idea, draft, needs review, approved, scheduled, posted, repurposed, paused, rejected, or archived
- Campaign or theme
- Target audience
- Business goal supported
- Offer, product, service, or initiative connected to the post
- Customer insight or source material behind the post
- Core message
- Draft copy
- Visual or asset notes
- Call to action
- Link or destination if known
- Planned publish date
- Actual publish date
- Owner if known
- Approval notes
- Performance metrics if available
- Lessons learned
- Repurposing opportunities
- Open questions
- Last updated date
- Review date
- Confidence level
- Related customer segment
- Related proof or evidence
- Related advisor recommendation
- Reason paused, rejected, or archived when applicable
2. Planning views
Add viewer content that helps me see:
- Upcoming posts
- Drafts needing review
- Approved or scheduled posts
- Posted content
- Posts grouped by channel, status, campaign, audience, offer, and theme
- Posts missing a clear goal, audience, call to action, owner, approval, or publish date
- Content gaps by channel or audience
- Repurposing opportunities
- Recent performance notes
- Posts due for review
- Posts with unsupported claims
- Posts connected to current offers, goals, and campaigns
3. Marketing Advisor workflow
Update the Marketing Advisor so it can:
- Review post ideas against positioning, audience, offers, campaigns, and proof
- Identify missing context before posts are written
- Suggest content themes based on customer insights and business goals
- Improve post clarity without inventing unsupported claims
- Recommend what to repurpose, pause, or test next
- Flag claims, themes, or calls to action that need better proof
4. Cross-advisor review
Have these advisors review the social media system:
- Strategy Advisor: connection to goals and priorities
- Marketing Advisor: audience, message, channel, proof, and campaign logic
- Sales Advisor: buyer objections, offer clarity, and lead quality
- Product Advisor: product claims, roadmap sensitivity, and customer feedback
- Operations Advisor: approval workflow and publishing cadence
- AI Advisor: repeatable content assistance opportunities and quality checks
- Risk Advisor: claims, compliance, brand, privacy, and reputation risks
5. Question Library
Add useful questions such as:
- Which audience is this post for?
- What business goal does this post support?
- What offer, service, product, or initiative is connected to this post?
- What proof or customer insight supports this message?
- What should the reader do next?
- Who needs to approve this before publishing?
- What platform-specific constraint should shape the post?
- What result should we review after it is posted?
6. Suggested prompts
Add prompts I can use later, including:
- Add this social media post idea: [details].
- Turn these notes into a social media post plan.
- Show me posts that need approval this week.
- Ask the Marketing Advisor to review next week's post plan.
- Create post drafts from these customer insights without inventing claims.
- Review posted content and identify what should be repurposed.
- Update this post as published and add performance notes: [details].
7. Maintenance behavior
Make sure the social media system can be reviewed over time:
- Posts with missing publish dates should appear in the Review Queue.
- Drafts stuck too long should be flagged.
- Posted items should remain visible as history.
- Rejected posts should keep the reason they were rejected.
- Performance notes should connect back to content themes, offers, and campaigns.
- Missing proof should create open questions.
- Changes should update the local website viewer.
- The system should work with the current marketing, offers, customers, evidence, metrics, and review queue records when they exist.
- The system should not require connecting to social platforms or publishing tools.
Before building:
- Inspect the existing Marketing, Customers, Offers, Product, Evidence, Metrics, Decisions, Review Queue, and Advisor areas.
- Decide whether this should extend an existing Marketing page or needs a new focused social media page under the appropriate existing section.
- If you are unsure about channels, approval workflow, publishing cadence, or whether the business wants drafts, planning, tracking, or all three, ask clarifying questions before building.
- Then add the smallest useful planning and tracking system that fits the current Groundwork status and can grow over time.
Build prompt
Customer Research Library
A detailed build prompt for capturing interviews, feedback, objections, testimonials, customer language, proof, and market signals without duplicating existing customer records.Open full prompt
Build a full Customer Research Library inside my Groundwork system.
Goal:
Create a practical customer research library that helps me capture, organize, review, and reuse customer interviews, feedback, objections, testimonials, buying triggers, churn reasons, feature requests, customer language, and market signals while keeping Groundwork's source of truth accurate.
Current Groundwork system rules:
- Start by inspecting the current Groundwork folder, source files, website pages, advisor files, logs, manuals, navigation hubs, and current state of the system.
- Fit this feature into the existing Groundwork layout, naming, card patterns, advisor patterns, source structure, Question Library, Review Queue, Source Health, Change Log, and local website viewer.
- Do not take over, replace, rebrand, redesign, or reorganize the whole system. Add this feature as an extension of whatever currently exists.
- If a similar feature, page, source file, advisor workflow, or question set already exists, improve or extend it instead of creating a duplicate.
- Keep the canonical source of truth in /src/source. Update source records first, then update the local website viewer.
- Treat website pages as viewer pages only, not as the business source of truth.
- Unknown, missing, ambiguous, or unsupported information becomes Question Library items. Do not invent business facts.
- Preserve completed questions and label every question clearly as Open, Completed, Deferred, or Not Applicable.
- Keep advisor knowledge separated by advisor. Do not merge advisor knowledge banks.
- Do not add remote services, analytics, cloud dependencies, package managers, scripts, servers, databases, or tracking.
- Reuse existing Groundwork visual layout and navigation patterns. Add page cards only in the appropriate existing section or tool hub; do not add unnecessary top-level navigation.
- If the request could affect source integrity, website sync, advisor behavior, local-only operation, privacy, navigation, file structure, or governance rules, perform a System Impact Review before changing the system.
- Create the required backup before major structural changes when the current Groundwork system calls for it.
- Log meaningful changes in the existing Groundwork logs.
- If you are unsure how this should fit the current system, what page or source file should own it, or which behavior the user wants, ask concise clarifying questions before building. Ask only what is needed to avoid a bad assumption.
System to create:
1. Customer research source structure
Track each research record with:
- Research title or short label
- Source type: customer interview, prospect call, sales note, support note, survey, review, testimonial, website feedback, email, meeting note, social comment, churn note, win-loss note, or other
- Customer or segment if known
- Date collected if known
- Source material or evidence reference
- Sensitivity level and privacy notes
- Consent or usage notes for quotes and testimonials
- Raw observation or safe summary
- Important customer quotes when safe to store
- Pain points
- Desired outcomes
- Buying triggers
- Objections
- Alternatives considered
- Decision criteria
- Customer language and phrases
- Feature requests or improvement ideas
- Pricing signals
- Proof, results, or testimonial value
- Churn, hesitation, or dissatisfaction signals
- Related offers, products, services, campaigns, backlog items, decisions, assumptions, risks, and metrics
- Related advisor recommendations
- Open questions
- Confidence level
- Last updated date
- Review date
2. Customer research views
Add viewer content that helps me see:
- Recent research
- Priority insights
- Customer language worth reusing
- Top pain points and desired outcomes
- Common objections and alternatives
- Research grouped by customer segment, source type, offer, product area, and theme
- Testimonials or proof candidates
- Feedback that should create backlog items
- Feedback that affects marketing, sales, offers, product, or support
- Research records with weak evidence, unclear source, privacy concerns, or missing review dates
3. Advisor workflows
Update relevant advisors so they can use customer research:
- Strategy Advisor: customer focus, market signals, and priority implications
- Product Advisor: feature requests, product gaps, roadmap evidence, and product-market fit signals
- Marketing Advisor: customer language, positioning, proof, themes, and campaign ideas
- Sales Advisor: objections, buying triggers, alternatives, and follow-up angles
- Finance Advisor: pricing signals, willingness to pay, and segment quality
- Operations Advisor: delivery friction and customer experience patterns
- Risk Advisor: privacy, claims, promises, and unsupported conclusions
4. Question Library
Add useful questions such as:
- Which customer segment does this feedback represent?
- What customer problem or desired outcome does this reveal?
- What offer, product, or service does this affect?
- Is this feedback common or isolated?
- What exact customer language should we preserve?
- What evidence supports this insight?
- Can this quote or testimonial be used externally?
- What decision, assumption, backlog item, or marketing message should this update?
5. Suggested prompts
Add prompts I can use later, including:
- Add this customer research note: [details].
- Turn these customer notes into source-of-truth updates and open questions.
- Ask the Product Advisor and Marketing Advisor to review this customer feedback.
- Show me the strongest customer proof we can safely use.
- Show me the top objections and what we know about them.
- Turn this interview into themes, quotes, backlog candidates, and advisor updates.
- Review customer research for gaps before we make this decision: [decision].
6. Maintenance behavior
Make sure the customer research library can be reviewed over time:
- Sensitive notes should be labeled clearly.
- Unsupported conclusions should become assumptions or open questions.
- Research that affects offers, product, sales, marketing, decisions, assumptions, risks, metrics, or backlog items should update those areas.
- Old research should be marked stale when it may no longer represent the current market.
- Research should not silently overwrite confirmed source records without preserving context.
- Changes should update the local website viewer.
Before building:
- Inspect the existing Customers, Offers, Product, Sales, Marketing, Evidence, Decisions, Assumptions, Metrics, Review Queue, and Advisor areas.
- Decide whether this should extend an existing Customers page or needs a new focused customer research page under the appropriate existing section.
- If you are unsure about privacy, quote usage, source reliability, customer segments, or how much raw feedback should be stored, ask clarifying questions before building.
- Then add the smallest useful customer research system that fits the current Groundwork status and can grow over time.
Build prompt
Decision Review Board
A detailed build prompt for tracking important decisions, rationale, assumptions, review dates, outcomes, reversals, and advisor input.Open full prompt
Build a full Decision Review Board inside my Groundwork system.
Goal:
Create a practical decision review board that helps me track important business decisions, options considered, rationale, assumptions, risks, outcomes, review dates, reversals, and follow-up actions while keeping Groundwork's source of truth accurate.
Current Groundwork system rules:
- Start by inspecting the current Groundwork folder, source files, website pages, advisor files, logs, manuals, navigation hubs, and current state of the system.
- Fit this feature into the existing Groundwork layout, naming, card patterns, advisor patterns, source structure, Question Library, Review Queue, Source Health, Change Log, and local website viewer.
- Do not take over, replace, rebrand, redesign, or reorganize the whole system. Add this feature as an extension of whatever currently exists.
- If a similar feature, page, source file, advisor workflow, or question set already exists, improve or extend it instead of creating a duplicate.
- Keep the canonical source of truth in /src/source. Update source records first, then update the local website viewer.
- Treat website pages as viewer pages only, not as the business source of truth.
- Unknown, missing, ambiguous, or unsupported information becomes Question Library items. Do not invent business facts.
- Preserve completed questions and label every question clearly as Open, Completed, Deferred, or Not Applicable.
- Keep advisor knowledge separated by advisor. Do not merge advisor knowledge banks.
- Do not add remote services, analytics, cloud dependencies, package managers, scripts, servers, databases, or tracking.
- Reuse existing Groundwork visual layout and navigation patterns. Add page cards only in the appropriate existing section or tool hub; do not add unnecessary top-level navigation.
- If the request could affect source integrity, website sync, advisor behavior, local-only operation, privacy, navigation, file structure, or governance rules, perform a System Impact Review before changing the system.
- Create the required backup before major structural changes when the current Groundwork system calls for it.
- Log meaningful changes in the existing Groundwork logs.
- If you are unsure how this should fit the current system, what page or source file should own it, or which behavior the user wants, ask concise clarifying questions before building. Ask only what is needed to avoid a bad assumption.
System to create:
1. Decision review source structure
Track each decision with:
- Decision title
- Decision status: proposed, needs input, decided, active, review due, changed, reversed, archived, or deferred
- Decision type: strategy, product, marketing, sales, finance, operations, technology, AI, people, risk, customer, offer, pricing, or other
- Date proposed
- Date decided if known
- Decision owner if known
- People or advisors consulted if known
- Options considered
- Chosen option
- Rationale
- Goals affected
- Business areas affected
- Customer impact
- Financial impact
- Operational impact
- Technology impact
- Risks and tradeoffs
- Assumptions behind the decision
- Evidence used
- Confidence level
- Expected outcome
- Success criteria or metrics
- Review date
- Outcome review notes
- Follow-up actions
- Related projects, initiatives, backlog items, metrics, customer research, risks, assumptions, and advisor recommendations
- Reason changed, reversed, deferred, or archived when applicable
- Last updated date
2. Decision review views
Add viewer content that helps me see:
- Decisions needing input
- Recently made decisions
- Decisions due for review
- Decisions with weak evidence
- Decisions with unresolved assumptions
- Decisions grouped by business area, status, owner, and review date
- Decisions that changed priorities, offers, products, finances, operations, or risks
- Decisions that need advisor review
- Decisions that should update metrics or source health
3. Advisor workflows
Update relevant advisors so they can review decisions:
- Strategy Advisor: strategic fit, focus, tradeoffs, and opportunity cost
- Product Advisor: customer impact, product direction, and roadmap implications
- Finance Advisor: pricing, margin, cash, cost, and return implications
- Marketing Advisor: positioning, messaging, channel, and campaign implications
- Sales Advisor: buyer impact, objections, and conversion implications
- Operations Advisor: delivery complexity, ownership, and process impact
- Technology Advisor: technical feasibility, security, and maintainability
- AI Advisor: practical AI opportunities or risks created by the decision
- People Advisor: accountability, capacity, and training implications
- Risk Advisor: risk exposure, mitigation, and evidence gaps
4. Question Library
Add useful questions such as:
- What decision is being made?
- What options were considered?
- Why was this option chosen?
- What goals does this decision support?
- What assumptions does this decision depend on?
- What evidence supports the decision?
- What risk or tradeoff should be monitored?
- When should this decision be reviewed?
- What would cause us to reverse or revise this decision?
- What source records need to change because of this decision?
5. Suggested prompts
Add prompts I can use later, including:
- Add this decision to the Decision Review Board: [details].
- Review decisions due this month and recommend what needs attention.
- Evaluate this proposed decision using all relevant advisors: [decision].
- Update this decision after the outcome review: [details].
- Show me decisions that depend on weak assumptions.
- Show me decisions that changed goals, priorities, risks, or metrics.
- Mark this decision reversed and update affected source records.
6. Maintenance behavior
Make sure the decision review board can be reviewed over time:
- Decisions due for review should appear in the Review Queue.
- Decisions should link to affected assumptions, risks, metrics, initiatives, backlog items, offers, customer research, and advisor recommendations when those exist.
- Changed or reversed decisions should preserve the original rationale and the reason for the change.
- Decisions should not silently overwrite history.
- Decisions with missing evidence should create open questions.
- Changes should update the local website viewer.
Before building:
- Inspect the existing Decisions, Assumptions, Risks, Metrics, Initiatives, Product, Offers, Customer, Review Queue, Evidence, and Advisor areas.
- Decide whether this should improve the existing Decisions page or needs a new focused Decision Review Board page under the appropriate existing section.
- If you are unsure about review cadence, decision statuses, owners, or which decisions deserve board-level tracking, ask clarifying questions before building.
- Then add the smallest useful decision review system that fits the current Groundwork status and can grow over time.
Build prompt
Metrics and KPI System
A detailed build prompt for defining, tracking, reviewing, and using business metrics tied to goals, decisions, source health, and advisor recommendations.Open full prompt
Build a full Metrics and KPI System inside my Groundwork system.
Goal:
Create a practical metrics and KPI system that helps me define, track, review, and use business metrics tied to goals, priorities, offers, customers, products, operations, finances, risks, and decisions while keeping Groundwork's source of truth accurate.
Current Groundwork system rules:
- Start by inspecting the current Groundwork folder, source files, website pages, advisor files, logs, manuals, navigation hubs, and current state of the system.
- Fit this feature into the existing Groundwork layout, naming, card patterns, advisor patterns, source structure, Question Library, Review Queue, Source Health, Change Log, and local website viewer.
- Do not take over, replace, rebrand, redesign, or reorganize the whole system. Add this feature as an extension of whatever currently exists.
- If a similar feature, page, source file, advisor workflow, or question set already exists, improve or extend it instead of creating a duplicate.
- Keep the canonical source of truth in /src/source. Update source records first, then update the local website viewer.
- Treat website pages as viewer pages only, not as the business source of truth.
- Unknown, missing, ambiguous, or unsupported information becomes Question Library items. Do not invent business facts.
- Preserve completed questions and label every question clearly as Open, Completed, Deferred, or Not Applicable.
- Keep advisor knowledge separated by advisor. Do not merge advisor knowledge banks.
- Do not add remote services, analytics, cloud dependencies, package managers, scripts, servers, databases, or tracking.
- Reuse existing Groundwork visual layout and navigation patterns. Add page cards only in the appropriate existing section or tool hub; do not add unnecessary top-level navigation.
- If the request could affect source integrity, website sync, advisor behavior, local-only operation, privacy, navigation, file structure, or governance rules, perform a System Impact Review before changing the system.
- Create the required backup before major structural changes when the current Groundwork system calls for it.
- Log meaningful changes in the existing Groundwork logs.
- If you are unsure how this should fit the current system, what page or source file should own it, or which behavior the user wants, ask concise clarifying questions before building. Ask only what is needed to avoid a bad assumption.
System to create:
1. Metrics and KPI source structure
Track each metric with:
- Metric name
- Metric category: revenue, profit, cash, sales, marketing, product, customer, operations, delivery, quality, retention, AI workflow, people, risk, or other
- Definition in plain language
- Formula or calculation if known
- Why it matters
- Related goal
- Related business area
- Owner if known
- Data source
- Data collection method
- Update cadence
- Current value if known
- Baseline value if known
- Target value if known
- Thresholds or warning levels if known
- Trend if known
- Reporting period
- Last updated date
- Next review date
- Confidence level
- Evidence or source material
- Related offers, products, campaigns, customer segments, initiatives, decisions, assumptions, risks, backlog items, and advisor recommendations
- Open questions
- Notes about data quality, missing data, or manual collection
2. Metrics views
Add viewer content that helps me see:
- Priority metrics
- Metrics tied to active goals
- Metrics missing current values
- Metrics with unclear definitions
- Metrics with weak data sources
- Metrics due for review
- Metrics grouped by category, business area, owner, cadence, and confidence
- Metrics moving in the wrong direction when trend is known
- Metrics that should influence current decisions
- Metrics that need better source data before they can be trusted
3. Advisor workflows
Update relevant advisors so they can use metrics:
- Strategy Advisor: goal alignment, focus, and tradeoffs
- Finance Advisor: revenue, margin, cash, cost, and profitability measures
- Marketing Advisor: campaign, audience, content, lead, and conversion signals
- Sales Advisor: pipeline, conversion, objection, follow-up, and win-rate signals
- Product Advisor: adoption, usage, feedback, roadmap, and product-market fit signals
- Operations Advisor: delivery, quality, cycle time, capacity, and workflow signals
- AI Advisor: AI workflow value, quality, time savings, and human review signals
- People Advisor: capacity, role clarity, training, and accountability signals
- Risk Advisor: warning indicators, exposure, evidence gaps, and mitigation tracking
4. Question Library
Add useful questions such as:
- What metric best shows progress toward this goal?
- How is this metric defined?
- Where does the data come from?
- Who owns updating this metric?
- How often should it be reviewed?
- What is the current value?
- What target or threshold matters?
- What decisions should this metric influence?
- What data quality issue could make this metric misleading?
- What metric is missing from this business area?
5. Suggested prompts
Add prompts I can use later, including:
- Add this metric to Groundwork: [details].
- Review metrics tied to current goals and show what is missing.
- Ask the Finance Advisor to review financial metrics and data gaps.
- Show me metrics that need updated values this week.
- Create a one-page KPI summary for the current business.
- Review this decision against the metrics it affects: [decision].
- Identify which metrics would make advisor recommendations more useful.
6. Maintenance behavior
Make sure the metrics and KPI system can be reviewed over time:
- Metrics due for review should appear in the Review Queue.
- Metrics with missing values or unclear definitions should create open questions.
- Metrics should link to goals, decisions, initiatives, offers, product, marketing, sales, finance, operations, risks, assumptions, and advisor outputs when those exist.
- Metrics should not be treated as reliable when the source, definition, or confidence is weak.
- Stale metrics should be marked stale, not silently deleted.
- Changes should update the local website viewer and source health.
Before building:
- Inspect the existing Metrics, Goals, Strategy, Finance, Sales, Marketing, Product, Operations, Risks, Assumptions, Decisions, Initiatives, Review Queue, Evidence, and Advisor areas.
- Decide whether this should improve the existing Metrics page or needs a focused KPI dashboard under the appropriate existing section.
- If you are unsure about metric definitions, data sources, review cadence, targets, owners, or whether a metric should be tracked, ask clarifying questions before building.
- Then add the smallest useful metrics and KPI system that fits the current Groundwork status and can grow over time.
More build ideas
Other workflows users can add to Groundwork.
These ideas can become build prompts using the same pattern: source records first, questions for missing information, advisor review, viewer updates, and maintenance behavior.
Customer interview library
Sales objection tracker
Offer improvement queue
Pricing review board
Monthly business review dashboard
AI workflow registry
Content repurposing tracker
Hiring and capacity review
Vendor and tool review
Risk register
Decision review calendar
Customer proof library
Build with context
Groundwork gets more useful as the prompt library grows.
Use these templates as starting points, then shape them around your own goals, customers, offers, operating reality, and decision style.
