orientation

Documents roadmap phases and validates changes via a six-step workflow.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/yiwei79/azoth --skill orientation-yiwei79
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orientation
Source: https://github.com/yiwei79/azoth/tree/main/.opencode/skills/orientation
Command: npx skills add https://github.com/yiwei79/azoth --skill orientation-yiwei79

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It documents and provides the historical and current roadmap phases and the expanded development workflow, enabling consistent planning governance and roadmap alignment for azoth.

Core Features & Use Cases

  • Provides historical Phase Roadmap context (v0.1.0) and active v0.2.0-p4 stabilization notes.
  • Documents how to align backlog and roadmap edits with architecture references and bootstrap state.
  • Guides users through the expanded development workflow so agents load this skill only for planning and roadmapping tasks.

Quick Start

Open this skill and follow the six-step workflow to plan or edit roadmap alignments.

Frequently Asked Questions about orientation

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

FAQPage Schema
How do I verify architecture context before making backlog edits?

The expanded development workflow uses a six-step process to verify scope, architecture context, and memory capture before allowing backlog edits or roadmap changes, ensuring consistent planning governance and alignment.

What is the current roadmap phase used for planning and governance?

The current roadmap phase for planning governance is v0.2.0-p4 stabilization, documented alongside historical v0.1.0 context to maintain consistent roadmap alignment and guide active development planning.

How do I align roadmap edits with bootstrap state and architecture references?

You align roadmap edits by applying the six-step workflow to validate scope and architecture context against bootstrap state, root CLAUDE.md, azoth.yaml, and .azoth/roadmap-specs/v0.2.0 references before applying changes.

Do I need to load the planning workflow skill for every development task?

No, you do not need to load it for every task. The expanded development workflow guides agents to load this skill specifically for planning and roadmapping tasks rather than general development work.

What references should I check for roadmap validation and alignment?

For roadmap validation and alignment, check references to root CLAUDE.md, azoth.yaml, and .azoth/roadmap-specs/v0.2.0 to verify scope, architecture context, and memory capture before applying changes.