Company-as-Code Knowledge Bundle Builder
Interviews a founder domain by domain and writes typed, cross-linked markdown files agents can trust, with open items marked.
Before & after
Same prompt, same agent — the only difference is the skill.
You could create a folder structure for your company documentation and knowledge base. Using markdown files makes them easy to version control and collaborate on with your team. You'd want sections for different aspects of the business - strategy, marketing, operations, and other key areas. It's good to keep everything organized and linked together with cross-references. Some people use a wiki approach for this kind of thing. You'd need to think about what information matters most for your team and how to organize it logically. Would you like suggestions on what sections to include? Different companies structure this differently based on their focus.
COMPANY AS CODE - 12 PHASE INTERVIEW OUTPUT
Generated structure: company_docs/
index.md (frontmatter: type:company, name:"AgentVolt SaaS", created:2026-07-31)
foundation/
mission.md
values.md
vision_3_year.md
strategy/
market_positioning.md
differentiation.md
competitive_analysis.md
financial/
unit_economics.md
revenue_model.md
burn_rate_projection.md
sales/
go_to_market.md
target_customer_profile.md
pricing_tiers.md
marketing/
channel_strategy.md
messaging_framework.md
content_calendar.md
product/
roadmap_q3.md
technical_architecture.md
feature_prioritization.md
operations/
hiring_plan.md
finance_tooling.md
process_workflows.md
people/
culture_principles.md
compensation_bands.md
org_chart.md
legal/
entity_structure.md
compliance_checklist.md
governance/
decision_log.md
board_meeting_schedule.md
EACH FILE: Frontmatter metadata (type, owner, status), linked references to related docs, editable by team, committed to git. Interview guides founder through 2-3 questions per phase, generates polished markdown output. All docs readable by AI agents + humans.About this skill
Turn what lives in your head into a small set of markdown files that new hires and AI agents can actually rely on. It builds from zero, one domain at a time, and never fills gaps with plausible guesses.
What it does
- Starts with a minimum viable bundle (one-pager, ICP, offer and pricing, sales process, decision rights) instead of forcing 12 domains
- Asks the 3-5 questions per domain an employee or agent would need answered, including thresholds and approval limits
- Writes one concept per file with typed frontmatter: owner, status (decided / working assumption / open), review date, links
- Keeps every number in exactly one file and links to it, so the bundle cannot contradict itself
- Catches agent-hostile writing: relative dates, pronouns, rules without thresholds, aspirations stated as fact
What you get
Ready-to-save markdown files with paths, an updated index and change log, and a round summary listing open questions and the next domain to cover.
Best for
Founders documenting a new or early company, and teams preparing a knowledge base for an internal AI assistant.
SKILL.md preview
---
name: arquiteto-de-empresa
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →First VA Hiring and Handoff Kit
Hire your first assistant and hand work off: what to delegate first, a filtered job post, paid trial, safe access, handoff SOPs.
Claude Workspace Admin
Administer a Claude Team or Enterprise workspace: members, roles, connectors, SSO, offboarding. Scoped, verified, logged.
Delegation-Ready SOP for Recurring Tasks
Turns a task that lives in your head into an SOP a new VA or contractor can run solo, with decision rules, a done-check, and a handoff plan.
Company OS Designer
Sets up how your company runs: EOS-style, OKR, or custom, with accountability chart, quarterly priorities, scorecard, meeting cadence.