skills.rest
atstaeff
atstaeffCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

general

Guide technical writing, code review feedback, and principal engineer decision-making.

2|Updated Feb 8, 2026
Search Tags:#decision making#documentation#technical writing#communication#strategy#engineering leadership
One-click install
npx skills add https://github.com/atstaeff/ai-agents --skill general-atstaeff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: general
Source: https://github.com/atstaeff/ai-agents/tree/main/skills/general
Command: npx skills add https://github.com/atstaeff/ai-agents --skill general-atstaeff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides guidance on effective communication strategies and frameworks for making sound principal-level engineering decisions, improving clarity and impact in technical environments.

Core Features & Use Cases

  • Communication Best Practices: Learn to write clear documentation, effective code comments, and provide constructive feedback in code reviews.
  • Decision-Making Frameworks: Utilize structured approaches for evaluating technical options, documenting decisions, and managing ambiguity.
  • Use Case: When preparing a technical proposal, use this Skill to ensure your documentation is clear, concise, and tailored to your audience, and to structure your decision-making process for maximum impact.

Quick Start

Use the general skill to improve the clarity of a technical explanation for a non-technical audience.

Frequently Asked Questions about general

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

FAQPage Schema
How do I write an effective technical proposal for a non-technical audience?▼

To write an effective technical proposal, use communication frameworks to ensure your documentation is clear, concise, and tailored to your audience, balancing technical accuracy with accessibility for non-technical stakeholders.

What is the best way to structure technical decision-making for engineering leadership?▼

The best way to structure technical decision-making is using dedicated frameworks for evaluating options, managing ambiguity, and creating Architecture Decision Records (ADRs) to document rationale and build consensus among stakeholders.

How do I provide constructive feedback during code reviews?▼

Provide constructive code review feedback by applying communication best practices that focus on clarity and actionable guidance, ensuring comments are structured to improve code quality without friction.

Can I use this skill to balance innovation with stability in technical strategy?▼

Yes, you can use this skill to balance innovation with stability. It provides principal-level decision-making frameworks that address strategic trade-offs and consensus building in dynamic engineering environments.

When do I need to create Architecture Decision Records (ADRs)?▼

You need to create Architecture Decision Records (ADRs) when you must document technical decisions and manage ambiguity, providing a structured historical rationale for architectural choices to guide future engineering leadership.

Related Skills

Explore More Content & Communication Skills→
imvanzenimvanzen

technical-context-discovery

Inspect repository rules and analyze codebase patterns before code changes.

Community
Advanced
oldwinteroldwinter
5

stakeholder-alignment

Generate stakeholder alignment packs with briefs, maps, and communication plans.

Community
Advanced
fukukei23fukukei23

multi-llm-review

Coordinate independent multi-LLM reviews and integrate validated feedback into revisions.

Community
Advanced
jasonmeansjasonmeans
2

technical-roadmaps

Create and align technical roadmaps using the Rumelt framework.

Community
Intermediate