arquiteto-de-empresa
by alirezarezvaniarquiteto-de-empresa is a Company Architect skill that turns founder input into an OKF company knowledge base: linked Markdown files with YAML frontmatter, indexes, logs, and controlled types. Use it for Strategic Planning, company-as-code workflows, and phased interviews covering strategy, market, finance, product, operations, people, legal, and governance.
This skill scores 82/100, making it a solid listing candidate for directory users who want an agent to guide company creation/documentation as a structured markdown knowledge bundle. The repository provides enough trigger guidance, phase-by-phase workflow, templates, conformance rules, and helper scripts to reduce guesswork compared with a generic business-planning prompt, though adoption would be easier with clearer install and quick-start documentation.
- Strong triggerability: the frontmatter explicitly says to trigger for building, structuring, or documenting an entire company, including phrases like “company as code,” “company knowledge base for AI,” “OKF,” and “knowledge bundle.”
- Operationally clear workflow: the skill defines a sequential 12-phase interview and the phase playbook specifies objectives, question blocks, generated files, and update steps for index.md and log.md.
- Good agent leverage beyond prompting: references define OKF conformance and a controlled type vocabulary, while scripts support scaffolding, linting, and index generation for a version-controllable markdown bundle.
- No install command or README is present in the skill path, so users must infer installation from the broader repository or Agent Skills conventions.
- The workflow is ambitious and business-wide; users needing a narrow finance, legal, or GTM advisor may find the 12-phase OKF bundle approach heavier than necessary.
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. It is best for founders, operators, consultants, and strategic planning teams who want a company knowledge base that both humans and AI agents can read without translation.
Best-fit use cases and users
Use the arquiteto-de-empresa skill when you need to build or reorganize a company “as code”: strategy, market, finance, sales, marketing, product, operations, technology, people, legal, and governance in one linked structure. It fits early-stage venture design, business model documentation, internal company wikis, AI-readable operating systems, and arquiteto-de-empresa for Strategic Planning where decisions must be traceable over time.
What makes it different from a normal prompt
A generic prompt may produce a long business plan. This skill instead guides a phased interview and materializes the answer as files: one concept per .md, controlled type values, relative links, reserved index.md and log.md, and deterministic helper scripts. The key differentiator is not just business advice; it is a repeatable documentation format that can be linted, indexed, committed to Git, and extended by other agents.
Adoption considerations
The skill is strongest when you are willing to answer questions phase by phase. It is not ideal if you want a one-page pitch deck, legal advice, financial guarantees, or a finished company strategy without founder input. Some folder and file names are Portuguese-style, while the skill language is English, so teams should decide early whether to preserve the original structure or localize naming conventions.
How to Use arquiteto-de-empresa skill
arquiteto-de-empresa install and repository check
Install with:
npx skills add alirezarezvani/claude-skills --skill arquiteto-de-empresa
Then review the source path:
c-level-advisor/skills/arquiteto-de-empresa
Read SKILL.md first to understand the persona, trigger conditions, operating rules, and 12-phase flow. Next inspect references/phase_playbook.md, references/okf_conformance.md, and references/type_vocabulary.md; these files define what the agent should ask, how the Markdown bundle must be shaped, and which frontmatter type values are valid. Preview assets/frontmatter_template.md, assets/index_template.md, and assets/log_template.md before generating real company files.
Inputs that produce better outputs
The arquiteto-de-empresa usage pattern works best when the first request gives enough business context to start Phase 0. Include stage, business model, sector, jurisdiction, customer, current assets, and the desired output location.
Weak prompt:
“Help me structure my startup.”
Stronger prompt:
“Use arquiteto-de-empresa to create an OKF bundle for a B2B SaaS in Brazil that helps small clinics reduce missed appointments. Stage: MVP with 5 pilot customers. Model: monthly subscription. Need the first phases only: discovery, foundation, strategy, and market. Ask me questions in small blocks, mark unknowns as [ASSUMPTION], and generate conformant Markdown files with relative links.”
This improves results because the skill can choose the right phase, avoid premature detail, and create files that match the OKF rules.
Suggested workflow for a complete OKF bundle
Start with Phase 0 discovery, then proceed through the 12-phase playbook in order. In each phase, ask 3–5 questions, confirm the founder’s answers, generate the concept files, update the folder index.md, and add a decision entry to log.md. Do not ask the agent to dump all phases at once unless you only need a rough prototype; the skill is designed to reduce hallucinated strategy by interviewing before writing.
For strategic planning, run phases in decision order: foundation, strategy, market, financial model, sales, marketing, product, operations, tech, people, legal, and governance. Keep unresolved claims visible with [ASSUMPTION] so the bundle becomes a planning system, not a fake certainty generator.
Using the helper scripts
The repository includes Python tools that make the output more reliable. Use scripts/scaffold_bundle.py to create a skeleton, scripts/okf_linter.py to check conformance, and scripts/index_generator.py to regenerate concept tables in index.md. The scripts are standard-library oriented and support a Git workflow: generate, review diffs, lint, then commit. If your agent creates files manually, still run the linter before treating the bundle as canonical.
arquiteto-de-empresa skill FAQ
Is arquiteto-de-empresa only for new companies?
No. It is framed around building a company from scratch, but it can also document an existing company whose knowledge is scattered across docs, spreadsheets, chats, and founder memory. For an operating business, start by telling the agent what already exists and ask it to mark legacy facts, assumptions, and missing evidence separately.
How is this different from a business plan generator?
A business plan generator usually produces one narrative document. The arquiteto-de-empresa skill produces an OKF knowledge graph: many small Markdown concept files with consistent metadata and links. That makes it better for long-term maintenance, AI retrieval, Git diffs, and cross-functional planning. It is less convenient if you only need a polished investor-facing PDF.
Do beginners need to understand OKF first?
No, but they should understand the operating idea: one file per concept, typed frontmatter, links between related files, and a decision log. Reading references/okf_conformance.md before heavy use prevents common mistakes such as merging multiple concepts into one file or using inconsistent type labels.
When should I not use this skill?
Do not use it as a substitute for legal, tax, accounting, or regulated-industry professional review. Avoid it when the team cannot answer basic discovery questions, when the goal is only branding copy, or when you need confidential financial modeling without a secure execution environment. The skill structures decisions; it does not validate market truth by itself.
How to Improve arquiteto-de-empresa skill
Improve arquiteto-de-empresa results with stronger context
The highest-leverage improvement is better input quality. Provide real constraints: budget, runway, geography, target customer, sales motion, pricing hypotheses, team capacity, technology stack, regulatory exposure, and existing documents. Ask the agent to separate “known,” “assumed,” and “to validate” sections inside each concept file. This makes the OKF bundle useful for strategic planning rather than just descriptive documentation.
Common failure modes to watch
Watch for over-compressed files, missing frontmatter, invalid type values, weak relative links, and index.md pages that do not reflect the actual folder contents. Another common issue is overconfident business language when the founder has not supplied evidence. Require [ASSUMPTION] markers and update log.md whenever a major decision changes.
Iterate after the first generated bundle
After the first pass, review the bundle like a product backlog. Ask: Which concepts are too large? Which claims lack evidence? Which decisions need alternatives and rationale? Which links would help a future agent navigate from strategy to finance, product, or operations? Then ask the skill to split oversized files, add missing concept links, regenerate indexes, and record the changes in the decision log.
Extend the skill for your organization
Teams can improve arquiteto-de-empresa by adding company-specific templates, jurisdiction checklists, industry vocabulary, and validation gates. Keep the core OKF rules stable: one concept per file, mandatory type, relative links, reserved index.md and log.md, and script-based checks. If you localize folder names or add new concept types, update references/type_vocabulary.md so future agents remain consistent.