arquiteto-de-empresa
by alirezarezvaniarquiteto-de-empresa turns a founder’s business idea into a version-controlled OKF Markdown bundle with frontmatter, cross-links, index.md, log.md, and a 12-phase interview covering strategy, market, finance, product, operations, legal, and governance. Includes templates plus Python scaffold, linter, and index scripts.
This skill scores 84/100, which means it is a solid listing candidate for directory users who want an agent-led workflow to turn a founder interview into a version-controllable company knowledge base. It provides enough trigger guidance, phase structure, templates, references, and scripts to offer materially more leverage than a generic business-planning prompt, though installation and language/naming expectations need clearer packaging.
- Strong triggerability: the frontmatter explicitly names use cases such as building a company from scratch, company-as-code, OKF bundles, and AI-readable company wikis.
- Operationally substantive: the referenced 12-phase playbook defines objectives, questions, generated artifacts, and update steps for each phase rather than relying on a vague business-advisor prompt.
- Good agent leverage: OKF conformance rules, a controlled type vocabulary, templates, an example bundle, and Python tools for scaffolding, linting, and index generation make outputs more structured and reusable.
- No README or install command is present in the skill directory, so users must infer installation from the broader repository/tooling.
- The bundle structure uses Portuguese folder/file names while the skill description says it operates in English, which may create naming-language expectations to clarify before adoption.
Overview of arquiteto-de-empresa skill
What arquiteto-de-empresa is for
arquiteto-de-empresa is a Company Architect skill for turning a founder’s rough business idea into an OKF bundle: a version-controllable tree of Markdown files with YAML frontmatter, typed concepts, cross-links, index.md dashboards, and an append-only log.md. Instead of producing a one-shot business plan, the skill runs a phased interview and materializes the company as structured knowledge that humans and AI agents can read.
Best-fit users and decisions
This skill is best for founders, chief-of-staff operators, venture studios, consultants, and strategic planning teams who need a living company knowledge base, not just a pitch narrative. It fits early-stage company design, business model documentation, operating-system creation, and “company as code” workflows. arquiteto-de-empresa for Strategic Planning is especially useful when you want strategy, market, finance, sales, marketing, product, operations, tech, people, legal, and governance decisions connected in one repository.
What makes the skill different
The main differentiator is structure. The skill follows a 12-phase playbook, asks a few questions at a time, and writes one concept per .md file using a controlled type vocabulary. This makes the output easier to diff in Git, validate, index, and reuse by other agents. The included references and Python scripts support scaffolding, linting OKF conformance, and regenerating index tables.
When it may be too much
Do not install arquiteto-de-empresa skill if you only need a quick SWOT, a landing-page brief, or a short investor memo. The method is intentionally systematic. It works best when you are willing to answer staged questions, maintain files, and treat assumptions as draft knowledge rather than final truth.
How to Use arquiteto-de-empresa skill
Install and inspect the repository first
For a Claude skills workflow, install from the repository with:
npx skills add alirezarezvani/claude-skills --skill arquiteto-de-empresa
If your tool does not support that command, copy or reference the skill folder from c-level-advisor/arquiteto-de-empresa/skills/arquiteto-de-empresa. Before using it seriously, read SKILL.md, then references/phase_playbook.md, references/okf_conformance.md, and references/type_vocabulary.md. Preview assets/frontmatter_template.md, assets/index_template.md, and assets/log_template.md so you understand the file contract the agent is expected to satisfy.
Start with a complete discovery prompt
Good arquiteto-de-empresa usage starts with context, not a vague request. Instead of “build my company,” provide the initial facts the Phase 0 discovery needs:
- company idea and customer problem
- stage: idea, MVP, operating, or scaling
- business model: service, SaaS, marketplace, product, hybrid
- sector, country, and legal jurisdiction
- existing name, assets, constraints, and known assumptions
- desired output location, for example
./my-company-okf
A stronger prompt is: “Use arquiteto-de-empresa to create an OKF bundle for a B2B SaaS in Brazil that helps clinics reduce no-shows. We are at MVP stage, have no legal entity yet, and want files suitable for Git. Run Phase 0 first, ask only the necessary questions, mark unknowns as [ASSUMPTION], then scaffold the bundle.”
Follow the 12-phase workflow, not a dump
The skill is designed to interview in order: discovery, foundation, strategy, market, finance, sales, marketing, product, operations, tech, people, legal, and governance. Ask the agent to complete one phase, confirm the generated concepts, update the root index.md, and append log.md before moving on. This prevents shallow, inconsistent output and keeps strategic decisions traceable.
Use the helper scripts for quality control
The repository includes scripts/scaffold_bundle.py, scripts/okf_linter.py, and scripts/index_generator.py. Use them as implementation aids after the agent drafts content. The linter is important because OKF quality depends on details: every concept should be a separate Markdown file, frontmatter should include a valid type, and links should form a usable graph rather than isolated documents.
arquiteto-de-empresa skill FAQ
Is arquiteto-de-empresa only for new companies?
No. It is strongest for creating a business from scratch, but it can also document an existing company if you provide current strategy, processes, tools, finances, and org details. For an operating company, ask the skill to distinguish “current state,” “target state,” and [ASSUMPTION] items so the bundle does not rewrite reality as aspiration.
How is it better than an ordinary business-plan prompt?
A normal prompt often returns a polished but flat document. arquiteto-de-empresa produces a navigable knowledge system: typed Markdown concepts, reserved indexes, decision logs, and cross-links. That matters if you want future agents to retrieve company knowledge, update one concept without rewriting everything, or track how decisions changed over time.
Do I need to know OKF before using it?
No, but you should read the OKF conformance reference before trusting the output. The key rules are simple: one concept per file, YAML frontmatter with a valid type, reserved index.md and log.md, relative links between concepts, and assumptions marked clearly. Beginners can use the skill well if they follow the phased interview instead of asking for all files at once.
When should I not use this skill?
Skip this skill when speed matters more than structure, when the business is too confidential to share with an AI environment, or when you need legally binding advice. It can organize legal and governance concepts, but it is not a substitute for lawyers, accountants, or jurisdiction-specific compliance review.
How to Improve arquiteto-de-empresa skill
Improve arquiteto-de-empresa inputs before generating files
The biggest quality lever is input specificity. Provide real constraints: budget range, target customer, geography, founder skills, current traction, pricing hypotheses, sales motion, regulatory risks, and technology preferences. If something is unknown, say so. The skill’s [ASSUMPTION] convention is useful only when the agent knows which facts are missing.
Prevent common OKF failure modes
Watch for files that combine multiple concepts, missing type values, generic descriptions, broken relative links, and strategy claims that are not connected to market or financial assumptions. Ask the agent to run a conformance pass after each phase: “Check every generated concept against references/okf_conformance.md and references/type_vocabulary.md; list fixes before rewriting.”
Iterate phase outputs with decision criteria
After each phase, review for decision usefulness. A good foundation phase should clarify purpose, problem, values, and assumptions. A good finance phase should expose revenue model, cost structure, unit economics, pricing, and projections. A good operations phase should produce processes and runbooks that someone could execute. If the output reads like marketing copy, ask for sharper tradeoffs, dependencies, and rejected alternatives.
Extend the skill for your operating model
To improve arquiteto-de-empresa for your organization, add company-specific templates, type vocabulary extensions, or review checklists without breaking OKF basics. For example, a regulated healthcare startup might add compliance evidence fields; a venture studio might add investment committee status; a SaaS team might link PRDs to roadmap and architecture files. Keep extensions explicit so future agents can understand the bundle without hidden conventions.