Code
How fission-ai/openspec is laid out, and where to start for common changes.
There is no import map for this report yet.
Where to start reading
- Repository root
- Repository root
- Likely public API
- Likely public API
- Suggested starting pointAI
- Suggested starting pointAI
- Suggested starting pointAI
- Suggested starting pointAI
Find files for a task
AIAdd a new CLI command
- Import and register the command in the CLI router at src/cli/index.ts
Add a new artifact type to the spec system
- Extend the artifact type definitions in src/core/artifact-graph/types.ts to include the new artifact kind
- Add JSON schema constraints in src/core/artifact-graph/schema.ts to validate the new artifact structure
- Implement resolution logic in src/core/artifact-graph/resolver.ts to handle linking and dependency discovery for the new type
- Update src/core/artifact-graph/instruction-loader.ts to parse and expose instructions from the new artifact type
Add a new change proposal and stacked change
- Update openspec/changes/IMPLEMENTATION_ORDER.md to reflect the new change's position in the stack
Enhance interactive prompts and UI
- Use UI helpers from src/ui/ascii-patterns.ts for consistent terminal formatting and visual presentation
- Integrate the prompt into command flow via src/utils/interactive.ts for centralized input handling
Change the public API
Change build or automation
RepoPilot lists up to 500 files, so a file missing here may still exist.
- Files marked “likely” are guessed from their names.
- Some entry points named in the manifest are build output or are missing from the file list, so their source is not shown.