Feature Development Workflows

Workflows for designing, implementing, porting, and verifying features — from a single bug fix through multi-feature batches to kernel-scale system changes.

How to Start

Describe your intent to the assistant. Apogee routes to the right entry point:

  • “I want to add rate limiting” → feature.single_spec

  • “We need OAuth, API keys, and SSO” → multi_feature.identify_and_group

  • “There’s a null pointer crash in the parser” → bug_investigation.01_triage

  • “Port the Python engine to Rust” → code_porting.00_port_readiness_assessment

  • “Patch the crypto subsystem for RHEL” → large_systems.problem_scoping

Single Feature

Design and implement one feature through a governed lifecycle.

Step

Skill

What it does

1

feature.single_spec

Generate design.md and example.md from intent

2

feature.plan_scaffolding

Create plans.md, PLAN prompts, and review prompts

3

feature.plan_readiness

Re-review plan depth before execution

After plan execution, the post-feature workflow runs automatically.

Multi-Feature Design

Design and plan a batch of related features with cross-feature consistency checking.

Step

Skill

What it does

1

multi_feature.identify_and_group

Identify, validate, and group feature concepts into batches

2

multi_feature.per_slug_design_research

Research each feature against the codebase

3

multi_feature.batch_spec_generation

Generate design + example specs in batch

4

multi_feature.adversarial_synergy

Cross-feature consistency + code grounding review

5

multi_feature.generate_implementation_order

Create tiered implementation order with dependencies

6

multi_feature.test_definition_generation

Generate test definitions for the batch

7

multi_feature.doc_auto_update

Update documentation for new features

8

multi_feature.feature_set_planning_readiness

Final readiness gate before plan execution

9

multi_feature.plan_execution_checkpoint

Hard-stop gate for oversized plans

10

multi_feature.plan_rereview_confidence

Confidence rubric re-review during execution

Bug Investigation

Structured bug lifecycle from triage through validated fix.

Step

Skill

What it does

1

bug_investigation.01_triage

Classify severity, reproduce, identify affected area

2

bug_investigation.02_root_cause_analysis

Map symptom to root cause with CPG evidence

3

bug_investigation.03_fix_design

Design the fix with scope and risk assessment

4

bug_investigation.04_implement

Implement the fix

5

bug_investigation.05_validate

Verify the fix resolves the issue without regressions

Code Porting

Full porting pipeline from readiness assessment through release.

Step

Skill

What it does

0

code_porting.00_port_readiness_assessment

Assess whether the source is ready to port

0a

code_porting.00a_bootstrap_unit_tests_coverage

Bootstrap test coverage before porting

1

code_porting.01_source_hardening_optional

Optional hardening of the source before port

2

code_porting.02_port_charter_constraints

Define scope, constraints, and non-goals

3

code_porting.03_repo_scan_parity_surface

Scan target repo for parity gaps

4

code_porting.04_plan_slicing_scoring

Slice the port into scored plans

5

code_porting.05_plan_authoring_per_plan

Author each plan with evidence

6

code_porting.06_plan_execution_per_plan

Execute each plan

7

code_porting.07_hardening_per_plan_release_checklist

Per-plan release hardening

8

code_porting.08_final_audit_beta_release

Final audit and beta release gate

Pre-Port Hardening

Optional preparation suite run before code porting begins.

Step

Skill

What it does

0

pre_port_hardening.step0_baseline_inventory

Inventory current codebase state

1

pre_port_hardening.step1_refactor_porting_readiness

Refactor for porting readiness

2

pre_port_hardening.step2_unit_tests_coverage

Ensure unit test coverage

3

pre_port_hardening.step3_opt_in_integration_harness

Set up integration test harness

4

pre_port_hardening.step4_docs_changelog

Update docs and changelog

Large Systems Change

7-phase structured patch development for kernel-scale codebases.

Step

Skill

What it does

1

large_systems.problem_scoping

Define the problem boundary and affected subsystems

2

large_systems.structural_analysis

CPG-driven analysis of the change surface

3

large_systems.change_design

Design the change with upstream considerations

4

large_systems.test_baseline_capture

Capture test baselines before modification

5

large_systems.patch_implementation

Implement the patch

6

large_systems.cross_validation

Cross-validate against baselines and related subsystems

7

large_systems.upstream_submission

Prepare for upstream submission

Post-Feature Verification

Compound review suite that runs after implementation completes. Three scope levels: per-feature, per-tier, and release.

Step

Skill

What it does

1

post_feature.01_post_feature_review

Per-feature: stabilization, test discovery, adversarial check

2

post_feature.02_post_tier_review

Per-tier: cross-feature hardening, integration testing

3

post_feature.03_post_release_verification

Release: deep verification, all-suites re-run, archive

See Also