One-click install
npx skills add https://github.com/Vivekmano27/agent-orchestrator --skill steering-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: steering-docs
Source: https://github.com/Vivekmano27/agent-orchestrator/tree/main/plugins/project-orchestrator/skills/steering-docs
Command: npx skills add https://github.com/Vivekmano27/agent-orchestrator --skill steering-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates three persistent project context files (product.md, tech.md, structure.md) that guide every coding session by providing a consistent starting point for planning, architecture, and product direction.

Core Features & Use Cases

  • Creates three templates: product.md (product context), tech.md (technical context), and structure.md (project structure) placed in the .claude/steering/ directory.
  • Provides standardized sections (Vision, Problem Statement, Target Users, Success Metrics) to keep stakeholders aligned.
  • Used when kicking off a new project, refreshing project context, or when a user mentions steering documents, project context, product vision, or tech stack documentation.

Quick Start

Invoke this skill to generate three steering documents in .claude/steering/ for your current project.

Frequently Asked Questions about steering-docs

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

FAQPage Schema
How do I create project steering documents for consistent coding sessions?

Project steering documents are persistent context files that establish a consistent starting point for coding sessions by defining product vision, tech stack, and project structure.

How do I set up project context and tech stack documentation for a new project?

Set up project context by generating standardized templates for product vision, tech stack, and structure, providing stakeholders with consistent sections like Vision, Problem Statement, Target Users, and Success Metrics.

When do I need to use steering documents for my project?

You need steering documents when initializing a new project, updating project context, or when users reference product vision, tech stack documentation, or project structure to align stakeholders.

What is the best way to maintain product context across multiple coding sessions?

The best way to maintain product context is using persistent files in the .claude/steering/ directory that document the technical overview and product direction for every session.

Do I need any dependencies to generate project context files?

No dependencies are required to generate project context files; the skill creates product.md, tech.md, and structure.md independently with templated sections and standardized formatting.

Why does my coding session lose project context and technical overview?

Coding sessions lose project context without persistent steering documents; generating product.md, tech.md, and structure.md ensures consistent technical overview and product direction across sessions.