company-brief

Produce a SWE-focused company brief with Fact/Inference/Unknown claims and a Proceed/Pass conclusion.

4|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/ferez96/career-path-2026 --skill company-brief
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: company-brief
Source: https://github.com/ferez96/career-path-2026/tree/main/docs/skills/company-brief
Command: npx skills add https://github.com/ferez96/career-path-2026 --skill company-brief

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you replace scattered company rumors and incomplete notes with a structured, evidence-backed SWE-focused company brief that supports an explicit decision to proceed or pass.

Core Features & Use Cases

  • Evidence-first company research: Organizes claims into Fact, Inference, and Unknown with prioritized sources (official financials/IR, engineering content, then labeled anonymous reviews).
  • Personal fit comparison to your master profile: Produces a required short “Personal fit” section by comparing the company/team reality signals against data/master.yaml (role alignment, weights, constraints, and deal-breakers).
  • SWE execution and career decision framing: Covers technical landscape, AI/ML/data relevance (only when applicable), engineering culture, DX, remote/outsourcing signals, growth trajectory, stability risks, and ends with a Proceed/Pass-style recommendation plus confidence/gaps.

Quick Start

Use the company-brief skill to produce a SWE-focused brief for Acme, including personal fit versus your master.yaml, with a Proceed/Pass conclusion and a confidence section.

Frequently Asked Questions about company-brief

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure company due diligence research for a software engineering role?

Company due diligence research is structured by separating claims into Fact, Inference, and Unknown categories with prioritized sources. This approach covers technical landscape, engineering culture, DX, remote work signals, and stability risks to produce a decision-ready report.

What is the best way to evaluate engineering culture and technical stack fit before accepting a job?

Evaluating engineering culture and technical stack fit requires comparing company reality signals against your personal master profile. This personal fit comparison checks role alignment, weights, constraints, and deal-breakers to frame a clear career decision.

Can I generate a go/no-go decision memo for employer research using scattered company notes?

Yes, you can generate a go/no-go decision memo by organizing scattered company notes into an evidence-backed brief. The output concludes with Proceed, Proceed with conditions, Defer, or Pass, alongside a confidence score and verification gaps.

How does personal fit scoring work when researching a company's technical landscape?

Personal fit scoring works by comparing company technical landscape and engineering culture signals against a predefined master.yaml file. It evaluates role alignment, constraints, and deal-breakers to produce a required short personal fit section.

What sources should I prioritize for evidence-backed company research and stability risk analysis?

Evidence-backed company research prioritizes official financials and investor relations data first, followed by engineering content, then labeled anonymous reviews. This hierarchy ensures stability risks and technical landscape claims are reliably sourced.

When should I include AI and data relevance in a software engineering company brief?

AI and data relevance should be included in a software engineering company brief only when applicable to the specific role or company. This ensures the technical landscape analysis remains focused and relevant to your personal fit evaluation.