| name | add-feature |
| description | Add a new feature to an existing mobile application with requirements check, codebase exploration, brainstorming, planning, implementation, and review |
| source_type | command |
| source_file | commands/add-feature.md |
add-feature
Migrated from commands/add-feature.md.
Codex packaging notes
- Claude/Telar source files remain the source of truth; this file is the generated Codex adapter.
- Skill-local support files from the original Telar skill, such as
references/... or workflow/..., are packaged beside this SKILL.md.
- Repo-root references from the original Telar file, such as
agents/..., commands/..., scripts/..., resources/..., rules/..., hooks/..., or templates/..., are packaged at this plugin root.
- The original Telar orchestration source (
skills/orchestration/...) is packaged under source/skills/orchestration/... for exact-reference lookups; all other Telar skills exist here only as the generated adapters under the plugin-root skills/ directory.
- Resolve plugin-root paths from this generated skill directory via
../.. when reading support files or running packaged scripts.
- In Codex, this skill is the replacement for the Claude slash command
/tl-telar:add-feature; invoke it as $add-feature or through @tl-telar.
- Do not require Claude slash-command dispatch or Claude-only environment setup before following the workflow.
- When the original command says to load
skills/orchestration/<name>, load the generated Codex skill at ../orchestration-<name>/SKILL.md first. The original source copy also exists under ../../source/skills/orchestration/<name>/SKILL.md for exact Telar-source references.
Add Feature
Artifacts (REQUIREMENTS.md, RESEARCH.md, PLAN.md, PROGRESS.md) are written under tl-telar-spec/changes/<id>/ — see skills/requirements-gather.md → "Step 0" for change-id/domain resolution. Once the feature is complete, run node scripts/tl-telar-spec-archive.js <change-id> to merge into tl-telar-spec/truth/ and archive the change folder.
Add a new feature to an existing mobile application with structured exploration, requirements check, brainstorming, planning, and review.
Phase 0: Codebase Exploration (0-10%)
Load Rules
rules:
- codebase-first
Explore Project
Run scripts/project-detect.sh to detect platform, navigation, state management.
Codebase Scan
- Read
package.json or pubspec.yaml
- Scan existing component library
- Check design tokens / theme file
- Review existing test patterns
Phase 0.5: Requirements Check (10-20%)
Load Rules
rules:
- requirements-first
Load Skills
skills:
- requirements-gather
Check REQUIREMENTS.md
Does REQUIREMENTS.md exist?
├── YES — Is this feature defined in REQUIREMENTS.md?
│ ├── YES — Note the F-x / UI-x identifiers
│ │ → proceed to Phase 0.5B
│ └── NO — This is a new feature not yet in requirements
│ → invoke requirements-gather to add it
│ → proceed to Phase 0.5B
│
└── NO — REQUIREMENTS.md does not exist
→ invoke requirements-gather (full requirements gathering)
→ proceed to Phase 0.5B
Phase 0.5B: Design Asset Check
For each UI-x identified for this feature, check Design Assets table:
- Figma Final →
prompt-to-screen will use Mod B automatically
- Figma Draft/WIP or missing → user will be asked at spec generation time
Output
- Confirmed F-x / UI-x identifiers for this feature
- REQUIREMENTS.md updated if feature was new
Phase 1: Brainstorming (20-35%)
Load Skill
skills:
- brainstorm-first
Produce RESEARCH.md
- Read REQUIREMENTS.md first
- Focus on F-x requirements for this feature
- Architecture options that fit existing codebase
- State management approach (must match existing)
- Risk assessment tied to REQUIREMENTS.md Open Items
Blueprint Detection
- Check if feature matches an existing blueprint in
skills/blueprints/
- If yes, suggest it and adapt to existing codebase
Phase 2: Design & Planning (35-50%)
Load Skills
skills:
- plan-and-track
Produce PLAN.md
- Every task must reference F-x or UI-x from REQUIREMENTS.md
- Tasks feed into iterative-build-loop
Phase 3: Implementation (50-80%)
Load Relevant Skills
skills:
- Feature-specific skills
- Platform-specific skills (rn-* or flutter-*)
- Backend changes (if needed)
- Core logic
- UI components
- Navigation integration
Phase 4: Review & Integration (80-100%)
Verification Gate
skills:
- verification-before-completion
- review-gates
Stage 1A: REQUIREMENTS.md Compliance
- Does implementation cover all F-x for this feature?
- Are business rules from REQUIREMENTS.md implemented?
Stage 1B: PLAN.md Acceptance Criteria
- Are all tasks in PROGRESS.md marked complete?
- Do outputs match RESEARCH.md decisions?
Stage 2: Code Quality
- Follows existing architecture patterns
- Platform conventions respected
- Unit tests written
- Error and loading states handled
Integration
- Update PROGRESS.md to "Complete"
- Commit using mobile-commit-convention
- Archive: run
node scripts/tl-telar-spec-archive.js <change-id> — it moves the entire tl-telar-spec/changes/<id>/ folder (PLAN.md, PROGRESS.md, REQUIREMENTS.md, RESEARCH.md, and any TRACEABILITY.md together) to tl-telar-spec/changes/archive/<date>-<id>/ in one step, and merges any REQUIREMENTS.delta.md into tl-telar-spec/truth/. There is no separate .claude/archive/ location.
Completion Checklist
