openup-elaboration

Initialize and manage Elaboration phase activities - establish architecture baseline

6 stars

Best use case

openup-elaboration is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Initialize and manage Elaboration phase activities - establish architecture baseline

Teams using openup-elaboration should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/openup-elaboration/SKILL.md --create-dirs "https://raw.githubusercontent.com/GermanDZ/open-up-for-ai-agents/main/docs-eng-process/.claude-templates/skills/openup-elaboration/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/openup-elaboration/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How openup-elaboration Compares

Feature / Agent	openup-elaboration	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Initialize and manage Elaboration phase activities - establish architecture baseline

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Elaboration Phase

This skill guides you through the Elaboration phase of OpenUP - establishing the architecture baseline.

## When to Use

Use this skill when:
- Inception is complete and need to establish architecture baseline
- Need to design and validate system architecture
- Resolving high-risk technical elements
- Implementing architectural prototypes
- Checking if Elaboration phase is complete
- Getting guidance on next steps in Elaboration

## When NOT to Use

Do NOT use this skill when:
- Still defining project vision and scope (use `/openup-inception`)
- Architecture is stable and ready for incremental build (move to Construction)
- Need to create specific artifacts (use artifact skills)
- Looking for iteration planning (use `/openup-create-iteration-plan`)

## Success Criteria

After using this skill, verify:
- [ ] Phase status is clearly understood (initiated, in-progress, or complete)
- [ ] Architecture notebook is created or updated
- [ ] Technical risks are identified and mitigated
- [ ] Critical use cases are detailed
- [ ] Next steps are clearly defined

## Elaboration Overview

**Goal**: Design and implement the architecture, resolve high-risk elements
**Duration**: Typically 4-8 weeks
**Key Milestone**: Lifecycle Architecture

## Phase Objectives

1. Design and validate the architecture
2. Detail the critical use cases
3. Implement and test the architectural baseline
4. Refine the project plan with accurate estimates
5. Mitigate high-priority risks

## Completion Criteria

- [ ] Architecture notebook completed
- [ ] Critical use cases detailed (80%)
- [ ] Technical risks identified and mitigated
- [ ] Prototype(s) validated key architectural decisions
- [ ] Project plan refined with accurate estimates
- [ ] Stakeholder agreement on architecture

## Process

### 1. Read Project Status

Read `docs/project-status.md` to:
- Confirm phase is `elaboration`
- Check iteration goals
- Review active work items

### 2. Based on Activity

**`initiate`**: Start Elaboration phase
- Update `docs/project-status.md` to set `phase: elaboration`
- Create `docs/architecture-notebook.md` from template
- Review and refine `docs/risk-list.md` for technical risks
- Update `docs/roadmap.md` with elaboration tasks

**`check-status`**: Review progress
- Check all completion criteria above
- List what's done and what remains
- Identify blockers

**`next-steps`**: Get recommendations
- Suggest next tasks based on current state
- Prioritize by technical risk and dependencies

## Key Work Products

- **Architecture Notebook** (`docs/architecture-notebook.md`) - Architecture documentation
- **Design** (`docs/design/*.md`) - Detailed design documents
- **Use Cases** (`docs/use-cases/*.md`) - Detailed use cases
- **Developer Tests** - Test implementations
- **Updated Project Plan** (`docs/project-plan.md`)

## Recommended Team

For Elaboration phase work, create a team with:
- **architect** - Lead architecture design
- **developer** - Implement architectural baseline
- **tester** - Validate architecture through testing
- Add **analyst** for detailed requirements

## References

- Elaboration Phase: `docs-eng-process/openup-knowledge-base/practice-management/risk_value_lifecycle/guidances/concepts/phase-elaboration.md`
- Architect Role: `docs-eng-process/openup-knowledge-base/core/role/roles/architect-6.md`
- Architecture Notebook Template: `docs-eng-process/templates/architecture-notebook.md`

## See Also

- [openup-create-architecture-notebook](../../openup-artifacts/create-architecture-notebook/SKILL.md) - Generate architecture documentation
- [openup-shared-vision](../../openup-artifacts/shared-vision/SKILL.md) - Create shared technical vision
- [openup-create-use-case](../../openup-artifacts/create-use-case/SKILL.md) - Create detailed use cases
- [openup-detail-use-case](../../openup-artifacts/detail-use-case/SKILL.md) - Detail use cases with scenarios
- [openup-inception](../inception/SKILL.md) - Previous phase
- [openup-construction](../construction/SKILL.md) - Next phase after Elaboration

Related Skills

openup-transition

from GermanDZ/open-up-for-ai-agents

Initialize and manage Transition phase activities - deploy to users

openup-tdd-workflow

from GermanDZ/open-up-for-ai-agents

Guide Test-Driven Development cycle adapted for AI agents with a pragmatic approach

openup-sync-spec

from GermanDZ/open-up-for-ai-agents

Back-propagate pure refactors to stale artifacts; classify the diff, refuse behaviour-changes, propose targeted edits for approval (read-only by default)