LeandroBenjaminL/lend-ai / skills/_shared
_shared
VerifiedReferencias compartidas internas para skills SDD. No es una skill invocable.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 868 B |
| engram-convention.md | markdown | 5.3 KB |
| openspec-convention.md | markdown | 3.8 KB |
| persistence-contract.md | markdown | 7.7 KB |
| sdd-phase-common.md | markdown | 4.9 KB |
| skill-resolver.md | markdown | 5.2 KB |
| subagent-context.md | markdown | 3.3 KB |
openspec-convention.md
View on GitHub# OpenSpec File Convention (shared across all SDD skills)
## Directory Structure
```
openspec/
├── config.yaml <- Project-specific SDD config
├── specs/ <- Source of truth (main specs)
│ └── {domain}/
│ └── spec.md
└── changes/ <- Active changes
├── archive/ <- Completed changes (YYYY-MM-DD-{change-name}/)
└── {change-name}/ <- Active change folder
├── state.yaml <- DAG state (survives compaction)
├── exploration.md <- (optional) from sdd-explore
├── proposal.md <- from sdd-propose
├── specs/ <- from sdd-spec
│ └── {domain}/
│ └── spec.md <- Delta spec
├── design.md <- from sdd-design
├── tasks.md <- from sdd-tasks (updated by sdd-apply)
└── verify-report.md <- from sdd-verify
```
## Artifact File Paths
| Skill | Creates / Reads | Path |
|-------|----------------|------|
| orchestrator | Creates/Updates | `openspec/changes/{change-name}/state.yaml` |
| sdd-init | Creates | `openspec/config.yaml`, `openspec/specs/`, `openspec/changes/`, `openspec/changes/archive/` |
| sdd-explore | Creates (optional) | `openspec/changes/{change-name}/exploration.md` |
| sdd-propose | Creates | `openspec/changes/{change-name}/proposal.md` |
| sdd-spec | Creates | `openspec/changes/{change-name}/specs/{domain}/spec.md` |
| sdd-design | Creates | `openspec/changes/{change-name}/design.md` |
| sdd-tasks | Creates | `openspec/changes/{change-name}/tasks.md` |
| sdd-apply | Updates | `openspec/changes/{change-name}/tasks.md` (marks `[x]`) |
| sdd-verify | Creates | `openspec/changes/{change-name}/verify-report.md` |
| sdd-archive | Moves | `openspec/changes/{change-name}/` → `openspec/changes/archive/YYYY-MM-DD-{change-name}/` |
| sdd-archive | Updates | `openspec/specs/{domain}/spec.md` (merges deltas into main specs) |
## Reading Artifacts
```
Proposal: openspec/changes/{change-name}/proposal.md
Specs: openspec/changes/{change-name}/specs/ (all domain subdirectories)
Design: openspec/changes/{change-name}/design.md
Tasks: openspec/changes/{change-name}/tasks.md
Verify: openspec/changes/{change-name}/verify-report.md
Config: openspec/config.yaml
Main specs: openspec/specs/{domain}/spec.md
```
## Writing Rules
- Always create the change directory before writing artifacts
- If a file already exists, READ it first and UPDATE it (don't overwrite blindly)
- If the change directory already exists with artifacts, the change is being CONTINUED
- Use `openspec/config.yaml` `rules` section for project-specific constraints per phase
## Config File Reference
```yaml
# openspec/config.yaml
schema: spec-driven
context: |
Tech stack: {detected}
Architecture: {detected}
Testing: {detected}
Style: {detected}
rules:
proposal:
- Include rollback plan for risky changes
specs:
- Use Given/When/Then for scenarios
- Use RFC 2119 keywords (MUST, SHALL, SHOULD, MAY)
design:
- Include sequence diagrams for complex flows
- Document architecture decisions with rationale
tasks:
- Group by phase, use hierarchical numbering
- Keep tasks completable in one session
apply:
- Follow existing code patterns
tdd: false # Set to true to enable RED-GREEN-REFACTOR
test_command: ""
verify:
test_command: ""
build_command: ""
coverage_threshold: 0
archive:
- Warn before merging destructive deltas
```
## Archive Structure
When archiving, the change folder moves to:
```
openspec/changes/archive/YYYY-MM-DD-{change-name}/
```
Use today's date in ISO format. The archive is an AUDIT TRAIL — never delete or modify archived changes.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |