Menu
Add a new feature to an existing mobile application with requirements check, codebase exploration, brainstorming, planning, implementation, and review
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
End-to-end orchestrated execution. Takes a feature description and drives the entire pipeline — plan, plan review (3 fresh reviewers), WU decomposition, 4-phase execution loop per WU, final review, COMMIT-READY emit. Honors user's git policy (no auto-commit).
`--default-domain` comes from the project-detect framework signal (orchestrator Step 5b / project-context); it only decides how UI files with no strong path marker are classified. `--risk-tier` is the WU's `risk_tier` fi
**Capture the WU baseline ONCE per WU, before attempt 1 (NOT on retries).** This is what makes file-scope checks correct across a multi-WU run where the user has not yet committed prior WUs (per the `ben yapacagim` git p
This gate has **two interchangeable execution paths that MUST emit the identical aggregated verdict object** (Step 3). The prose path below is the canonical fallback and the single source of truth for reviewer prompts an
A baton-based system for building mobile features across multiple Claude Code sessions with persistent progress tracking and simulator verification between steps.
Set up end-to-end testing framework with CI integration
| 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 |
Migrated from commands/add-feature.md.
references/... or workflow/..., are packaged beside this SKILL.md.agents/..., commands/..., scripts/..., resources/..., rules/..., hooks/..., or templates/..., are packaged at this plugin root.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.../.. when reading support files or running packaged scripts./tl-telar:add-feature; invoke it as $add-feature or through @tl-telar.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.Artifacts (REQUIREMENTS.md, RESEARCH.md, PLAN.md, PROGRESS.md) are written under
tl-telar-spec/changes/<id>/— seeskills/requirements-gather.md→ "Step 0" for change-id/domain resolution. Once the feature is complete, runnode scripts/tl-telar-spec-archive.js <change-id>to merge intotl-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.
rules:
- codebase-first
Run scripts/project-detect.sh to detect platform, navigation, state management.
package.json or pubspec.yamlrules:
- requirements-first
skills:
- requirements-gather # only if REQUIREMENTS.md needs updating
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
For each UI-x identified for this feature, check Design Assets table:
prompt-to-screen will use Mod B automaticallyskills:
- brainstorm-first
skills/blueprints/skills:
- plan-and-track
skills:
- Feature-specific skills
- Platform-specific skills (rn-* or flutter-*)
skills:
- verification-before-completion
- review-gates
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.