id stringlengths 9 9 | dataset_name stringclasses 1
value | version stringclasses 1
value | task_type stringclasses 4
values | language stringclasses 1
value | domain stringclasses 8
values | difficulty stringclasses 3
values | request stringclasses 175
values | context dict | analysis stringclasses 117
values | plan listlengths 5 5 | expected_output dict | target_behavior listlengths 5 5 | tags listlengths 4 4 | metadata dict | reference_signal dict | repo_tree dict | README_excerpt stringclasses 3
values |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
jlv1_0101 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | medium | Extend the codebase to support caching while keeping the API stable. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"avoid adding new dependencies",
"limit changes to 2-3 files when possible",
"keep backwar... | This is a feature-planning request for caching in a CLI automation tool. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of caching in the CLI automation tool.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"Call... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0102 | JumpLander Agent Dataset | 1.0 | feature_planning | python | testing utility package | medium | Extend the codebase to support audit logging while keeping the API stable. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"ensure tests are easy to run locally",
"avoid adding new dependencies",
"keep backward compatibilit... | This is a feature-planning request for audit logging in a testing utility package. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of audit logging in the testing utility package.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0103 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | easy | Extend the codebase to support pagination while keeping the API stable. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"prefer explicit types and docstrings",
"keep backward compatibility",
"keep resp... | This is a feature-planning request for pagination in a Flask admin dashboard. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of pagination in the Flask admin dashboard.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"flask_admin_dashboard",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0104 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | medium | Introduce background cleanup jobs with minimal changes and clear validation steps. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"avoid adding new dependencies",
"prefer explicit types and docstrings",
"keep backward co... | This is a feature-planning request for background cleanup jobs in a CLI automation tool. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of background cleanup jobs in the CLI automation tool.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge ... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0105 | JumpLander Agent Dataset | 1.0 | feature_planning | python | data processing library | medium | Extend the codebase to support webhook delivery while keeping the API stable. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"src/",
"src/pipeline.py",
"src/transformers.py",
"src/io.py"
],
"constraints": [
"prefer explicit types and docstrings",
"support Python 3.10+",
"preserve current public A... | This is a feature-planning request for webhook delivery in a data processing library. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of webhook delivery in the data processing library.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cas... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"data_processing_library",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0106 | JumpLander Agent Dataset | 1.0 | feature_planning | python | web scraping toolkit | medium | Add background cleanup jobs to the web scraping toolkit without breaking existing behavior. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"scraper/",
"scraper/client.py",
"scraper/parsers.py",
"scraper/storage.py"
],
"constraints": [
"avoid adding new dependencies",
"limit changes to 2-3 files when possible",
... | This is a feature-planning request for background cleanup jobs in a web scraping toolkit. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of background cleanup jobs in the web scraping toolkit.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"web_scraping_toolkit",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0107 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | easy | Design a clean way to support JWT login in the current Python project. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"preserve current public API",
"keep response latency low",
"keep backward... | This is a feature-planning request for JWT login in a Flask admin dashboard. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of JWT login in the Flask admin dashboard.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"flask_admin_dashboard",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0108 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | hard | Extend the codebase to support audit logging while keeping the API stable. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"auth/",
"auth/jwt.py",
"auth/routes.py",
"auth/security.py"
],
"constraints": [
"keep response latency low",
"keep backward compatibility",
"avoid adding new dependencies"
],
"notes":... | This is a feature-planning request for audit logging in a authentication module. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of audit logging in the authentication module.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"authentication_module",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0109 | JumpLander Agent Dataset | 1.0 | feature_planning | python | web scraping toolkit | hard | Extend the codebase to support timezone-aware scheduling while keeping the API stable. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"scraper/",
"scraper/client.py",
"scraper/parsers.py",
"scraper/storage.py"
],
"constraints": [
"avoid adding new dependencies",
"ensure tests are easy to run locally",
"prefer explicit ty... | This is a feature-planning request for timezone-aware scheduling in a web scraping toolkit. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of timezone-aware scheduling in the web scraping toolkit.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important ed... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"web_scraping_toolkit",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0110 | JumpLander Agent Dataset | 1.0 | feature_planning | python | data processing library | easy | Add search filters to the data processing library without breaking existing behavior. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"src/",
"src/pipeline.py",
"src/transformers.py",
"src/io.py"
],
"constraints": [
"support Python 3.10+",
"ensure tests are easy to run locally",
"avoid adding new dependencies"
],
"no... | This is a feature-planning request for search filters in a data processing library. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of search filters in the data processing library.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"data_processing_library",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0111 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | medium | Design a clean way to support CSV export in the current Python project. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"keep response latency low",
"prefer explicit types and docstrings",
"ensur... | This is a feature-planning request for CSV export in a Flask admin dashboard. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of CSV export in the Flask admin dashboard.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"flask_admin_dashboard",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0112 | JumpLander Agent Dataset | 1.0 | feature_planning | python | testing utility package | hard | Extend the codebase to support pagination while keeping the API stable. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"keep response latency low",
"ensure tests are easy to run locally",
"support Python 3.10+"
],
"... | This is a feature-planning request for pagination in a testing utility package. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of pagination in the testing utility package.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0113 | JumpLander Agent Dataset | 1.0 | feature_planning | python | testing utility package | hard | Add audit logging to the testing utility package without breaking existing behavior. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"keep backward compatibility",
"support Python 3.10+",
"ensure tests are easy to run locally"
],
... | This is a feature-planning request for audit logging in a testing utility package. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of audit logging in the testing utility package.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0114 | JumpLander Agent Dataset | 1.0 | feature_planning | python | web scraping toolkit | easy | Add CSV export to the web scraping toolkit without breaking existing behavior. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"scraper/",
"scraper/client.py",
"scraper/parsers.py",
"scraper/storage.py"
],
"constraints": [
"support Python 3.10+",
"ensure tests are easy to run locally",
"keep respon... | This is a feature-planning request for CSV export in a web scraping toolkit. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of CSV export in the web scraping toolkit.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"web_scraping_toolkit",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0115 | JumpLander Agent Dataset | 1.0 | feature_planning | python | web scraping toolkit | medium | Add background cleanup jobs to the web scraping toolkit without breaking existing behavior. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"scraper/",
"scraper/client.py",
"scraper/parsers.py",
"scraper/storage.py"
],
"constraints": [
"preserve current public API",
"support Python 3.10+",
"keep respons... | This is a feature-planning request for background cleanup jobs in a web scraping toolkit. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of background cleanup jobs in the web scraping toolkit.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"web_scraping_toolkit",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0116 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | medium | Extend the codebase to support background cleanup jobs while keeping the API stable. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"prefer explicit types and docstrings",
"keep backward compatibility",
"support Python 3.10+"
],
"note... | This is a feature-planning request for background cleanup jobs in a CLI automation tool. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of background cleanup jobs in the CLI automation tool.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge ... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0117 | JumpLander Agent Dataset | 1.0 | feature_planning | python | background worker | medium | Add multi-file upload to the background worker without breaking existing behavior. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"worker/",
"worker/tasks.py",
"worker/scheduler.py",
"worker/queues.py"
],
"constraints": [
"preserve current public API",
"prefer explicit types and docstrings",
"... | This is a feature-planning request for multi-file upload in a background worker. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of multi-file upload in the background worker.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"background_worker",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0118 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | medium | Add webhook delivery to the authentication module without breaking existing behavior. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"auth/",
"auth/jwt.py",
"auth/routes.py",
"auth/security.py"
],
"constraints": [
"prefer explicit types and docstrings",
"keep backward compatibility",
"preserve current public API"
],
... | This is a feature-planning request for webhook delivery in a authentication module. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of webhook delivery in the authentication module.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"authentication_module",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0119 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | hard | Add search filters to the Flask admin dashboard without breaking existing behavior. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"prefer explicit types and docstrings",
"support Python 3.10+",
"keep back... | This is a feature-planning request for search filters in a Flask admin dashboard. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of search filters in the Flask admin dashboard.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases."... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"flask_admin_dashboard",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0120 | JumpLander Agent Dataset | 1.0 | feature_planning | python | background worker | medium | Extend the codebase to support background cleanup jobs while keeping the API stable. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"worker/",
"worker/tasks.py",
"worker/scheduler.py",
"worker/queues.py"
],
"constraints": [
"prefer explicit types and docstrings",
"limit changes to 2-3 files when possible",... | This is a feature-planning request for background cleanup jobs in a background worker. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of background cleanup jobs in the background worker.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge ca... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"background_worker",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0121 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | easy | Extend the codebase to support rate limiting while keeping the API stable. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"prefer explicit types and docstrings",
"keep backward compatibility",
"limit changes to 2... | This is a feature-planning request for rate limiting in a CLI automation tool. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of rate limiting in the CLI automation tool.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0122 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | medium | Add rate limiting to the CLI automation tool without breaking existing behavior. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"limit changes to 2-3 files when possible",
"keep backward compatibility",
"avoid adding new dep... | This is a feature-planning request for rate limiting in a CLI automation tool. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of rate limiting in the CLI automation tool.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0123 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | hard | Design a clean way to support caching in the current Python project. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"prefer explicit types and docstrings",
"ensure tests are easy to run locally",... | This is a feature-planning request for caching in a Flask admin dashboard. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of caching in the Flask admin dashboard.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"Ca... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"flask_admin_dashboard",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0124 | JumpLander Agent Dataset | 1.0 | feature_planning | python | web scraping toolkit | easy | Extend the codebase to support search filters while keeping the API stable. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"scraper/",
"scraper/client.py",
"scraper/parsers.py",
"scraper/storage.py"
],
"constraints": [
"prefer explicit types and docstrings",
"avoid adding new dependencies",
"su... | This is a feature-planning request for search filters in a web scraping toolkit. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of search filters in the web scraping toolkit.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"web_scraping_toolkit",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0125 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | hard | Design a clean way to support async task retries in the current Python project. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"auth/",
"auth/jwt.py",
"auth/routes.py",
"auth/security.py"
],
"constraints": [
"avoid adding new dependencies",
"preserve current public API",
"support Python 3.10+"
],
"notes": [
... | This is a feature-planning request for async task retries in a authentication module. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of async task retries in the authentication module.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cas... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"authentication_module",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0126 | JumpLander Agent Dataset | 1.0 | feature_planning | python | web scraping toolkit | hard | Introduce CSV export with minimal changes and clear validation steps. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"scraper/",
"scraper/client.py",
"scraper/parsers.py",
"scraper/storage.py"
],
"constraints": [
"keep response latency low",
"limit changes to 2-3 files when possible",
"pr... | This is a feature-planning request for CSV export in a web scraping toolkit. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of CSV export in the web scraping toolkit.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"web_scraping_toolkit",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0127 | JumpLander Agent Dataset | 1.0 | feature_planning | python | testing utility package | hard | Extend the codebase to support JWT login while keeping the API stable. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"prefer explicit types and docstrings",
"preserve current public API",
"limit change... | This is a feature-planning request for JWT login in a testing utility package. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of JWT login in the testing utility package.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0128 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | medium | Introduce audit logging with minimal changes and clear validation steps. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"auth/",
"auth/jwt.py",
"auth/routes.py",
"auth/security.py"
],
"constraints": [
"support Python 3.10+",
"ensure tests are easy to run locally",
"avoid adding new dependenc... | This is a feature-planning request for audit logging in a authentication module. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of audit logging in the authentication module.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"authentication_module",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0129 | JumpLander Agent Dataset | 1.0 | feature_planning | python | data processing library | medium | Add search filters to the data processing library without breaking existing behavior. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"src/",
"src/pipeline.py",
"src/transformers.py",
"src/io.py"
],
"constraints": [
"ensure tests are easy to run locally",
"prefer explicit types and docstrings",
"s... | This is a feature-planning request for search filters in a data processing library. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of search filters in the data processing library.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"data_processing_library",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0130 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | easy | Add audit logging to the CLI automation tool without breaking existing behavior. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"preserve current public API",
"keep response latency low",
"limit changes to 2-3 files when possible"
]... | This is a feature-planning request for audit logging in a CLI automation tool. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of audit logging in the CLI automation tool.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0131 | JumpLander Agent Dataset | 1.0 | feature_planning | python | testing utility package | hard | Extend the codebase to support pagination while keeping the API stable. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"keep backward compatibility",
"ensure tests are easy to run locally",
"avoi... | This is a feature-planning request for pagination in a testing utility package. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of pagination in the testing utility package.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0132 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | hard | Extend the codebase to support pagination while keeping the API stable. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"keep response latency low",
"preserve current public API",
"prefer explicit types... | This is a feature-planning request for pagination in a CLI automation tool. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of pagination in the CLI automation tool.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"C... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0133 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | hard | Extend the codebase to support multi-file upload while keeping the API stable. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"ensure tests are easy to run locally",
"prefer explicit types and docs... | This is a feature-planning request for multi-file upload in a Flask admin dashboard. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of multi-file upload in the Flask admin dashboard.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge case... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"flask_admin_dashboard",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0134 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | easy | Add background cleanup jobs to the FastAPI service without breaking existing behavior. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"api/",
"app/main.py",
"app/routes/auth.py",
"app/services/user_service.py"
],
"constraints": [
"support Python 3.10+",
"ensure tests are easy to run locally",
"limit changes to 2-3 files ... | This is a feature-planning request for background cleanup jobs in a FastAPI service. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of background cleanup jobs in the FastAPI service.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge case... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"fastapi_service",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0135 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | easy | Add search filters to the Flask admin dashboard without breaking existing behavior. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"avoid adding new dependencies",
"support Python 3.10+",
"prefer explicit types and docstri... | This is a feature-planning request for search filters in a Flask admin dashboard. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of search filters in the Flask admin dashboard.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases."... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"flask_admin_dashboard",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0136 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | easy | Add multi-file upload to the FastAPI service without breaking existing behavior. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"api/",
"app/main.py",
"app/routes/auth.py",
"app/services/user_service.py"
],
"constraints": [
"keep response latency low",
"preserve current public API",
"limit c... | This is a feature-planning request for multi-file upload in a FastAPI service. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of multi-file upload in the FastAPI service.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"fastapi_service",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0137 | JumpLander Agent Dataset | 1.0 | feature_planning | python | data processing library | hard | Extend the codebase to support webhook delivery while keeping the API stable. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"src/",
"src/pipeline.py",
"src/transformers.py",
"src/io.py"
],
"constraints": [
"preserve current public API",
"avoid adding new dependencies",
"limit changes to 2-3 files when... | This is a feature-planning request for webhook delivery in a data processing library. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of webhook delivery in the data processing library.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cas... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"data_processing_library",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0138 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | medium | Design a clean way to support background cleanup jobs in the current Python project. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"auth/",
"auth/jwt.py",
"auth/routes.py",
"auth/security.py"
],
"constraints": [
"prefer explicit types and docstrings",
"keep response latency low",
"avoid adding new dep... | This is a feature-planning request for background cleanup jobs in a authentication module. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of background cleanup jobs in the authentication module.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edg... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"authentication_module",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0139 | JumpLander Agent Dataset | 1.0 | feature_planning | python | web scraping toolkit | hard | Introduce audit logging with minimal changes and clear validation steps. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"scraper/",
"scraper/client.py",
"scraper/parsers.py",
"scraper/storage.py"
],
"constraints": [
"keep backward compatibility",
"limit changes to 2-3 files when possible",
"support Python 3... | This is a feature-planning request for audit logging in a web scraping toolkit. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of audit logging in the web scraping toolkit.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"web_scraping_toolkit",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0140 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | hard | Extend the codebase to support pagination while keeping the API stable. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"ensure tests are easy to run locally",
"keep response latency low",
"preserve cur... | This is a feature-planning request for pagination in a CLI automation tool. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of pagination in the CLI automation tool.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"C... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0141 | JumpLander Agent Dataset | 1.0 | feature_planning | python | web scraping toolkit | easy | Introduce audit logging with minimal changes and clear validation steps. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"scraper/",
"scraper/client.py",
"scraper/parsers.py",
"scraper/storage.py"
],
"constraints": [
"support Python 3.10+",
"prefer explicit types and docstrings",
"limit changes to ... | This is a feature-planning request for audit logging in a web scraping toolkit. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of audit logging in the web scraping toolkit.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"web_scraping_toolkit",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0142 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | hard | Introduce background cleanup jobs with minimal changes and clear validation steps. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"auth/",
"auth/jwt.py",
"auth/routes.py",
"auth/security.py"
],
"constraints": [
"keep response latency low",
"ensure tests are easy to run locally",
"preserve current public API... | This is a feature-planning request for background cleanup jobs in a authentication module. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of background cleanup jobs in the authentication module.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edg... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"authentication_module",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0143 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | medium | Add rate limiting to the authentication module without breaking existing behavior. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"auth/",
"auth/jwt.py",
"auth/routes.py",
"auth/security.py"
],
"constraints": [
"keep backward compatibility",
"keep response latency low",
"ensure tests are easy ... | This is a feature-planning request for rate limiting in a authentication module. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of rate limiting in the authentication module.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"authentication_module",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0144 | JumpLander Agent Dataset | 1.0 | feature_planning | python | data processing library | medium | Introduce background cleanup jobs with minimal changes and clear validation steps. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"src/",
"src/pipeline.py",
"src/transformers.py",
"src/io.py"
],
"constraints": [
"support Python 3.10+",
"ensure tests are easy to run locally",
"avoid adding new dependen... | This is a feature-planning request for background cleanup jobs in a data processing library. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of background cleanup jobs in the data processing library.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important e... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"data_processing_library",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0145 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | hard | Add caching to the CLI automation tool without breaking existing behavior. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"keep backward compatibility",
"preserve current public API",
"support Python 3.10+"
],
"not... | This is a feature-planning request for caching in a CLI automation tool. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of caching in the CLI automation tool.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"Call... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0146 | JumpLander Agent Dataset | 1.0 | feature_planning | python | background worker | easy | Design a clean way to support timezone-aware scheduling in the current Python project. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"worker/",
"worker/tasks.py",
"worker/scheduler.py",
"worker/queues.py"
],
"constraints": [
"avoid adding new dependencies",
"preserve current public API",
"limit c... | This is a feature-planning request for timezone-aware scheduling in a background worker. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of timezone-aware scheduling in the background worker.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge ... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"background_worker",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0147 | JumpLander Agent Dataset | 1.0 | feature_planning | python | data processing library | medium | Introduce JWT login with minimal changes and clear validation steps. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"src/",
"src/pipeline.py",
"src/transformers.py",
"src/io.py"
],
"constraints": [
"keep response latency low",
"limit changes to 2-3 files when possible",
"avoid adding new dependencies"
... | This is a feature-planning request for JWT login in a data processing library. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of JWT login in the data processing library.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"data_processing_library",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0148 | JumpLander Agent Dataset | 1.0 | feature_planning | python | web scraping toolkit | easy | Introduce timezone-aware scheduling with minimal changes and clear validation steps. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"scraper/",
"scraper/client.py",
"scraper/parsers.py",
"scraper/storage.py"
],
"constraints": [
"avoid adding new dependencies",
"support Python 3.10+",
"keep backward com... | This is a feature-planning request for timezone-aware scheduling in a web scraping toolkit. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of timezone-aware scheduling in the web scraping toolkit.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important ed... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"web_scraping_toolkit",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0149 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | medium | Introduce webhook delivery with minimal changes and clear validation steps. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"auth/",
"auth/jwt.py",
"auth/routes.py",
"auth/security.py"
],
"constraints": [
"avoid adding new dependencies",
"limit changes to 2-3 files when possible",
"support Python 3.10... | This is a feature-planning request for webhook delivery in a authentication module. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of webhook delivery in the authentication module.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"authentication_module",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0150 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | easy | Introduce audit logging with minimal changes and clear validation steps. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"keep response latency low",
"prefer explicit types and docstrings",
"support Python 3.10+"... | This is a feature-planning request for audit logging in a Flask admin dashboard. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of audit logging in the Flask admin dashboard.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"flask_admin_dashboard",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0151 | JumpLander Agent Dataset | 1.0 | feature_planning | python | data processing library | hard | Add audit logging to the data processing library without breaking existing behavior. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"src/",
"src/pipeline.py",
"src/transformers.py",
"src/io.py"
],
"constraints": [
"ensure tests are easy to run locally",
"keep response latency low",
"avoid adding new dependenc... | This is a feature-planning request for audit logging in a data processing library. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of audit logging in the data processing library.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"data_processing_library",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0152 | JumpLander Agent Dataset | 1.0 | feature_planning | python | testing utility package | easy | Introduce timezone-aware scheduling with minimal changes and clear validation steps. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"limit changes to 2-3 files when possible",
"keep backward compatibility",
"avoid adding n... | This is a feature-planning request for timezone-aware scheduling in a testing utility package. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of timezone-aware scheduling in the testing utility package.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0153 | JumpLander Agent Dataset | 1.0 | feature_planning | python | web scraping toolkit | medium | Add audit logging to the web scraping toolkit without breaking existing behavior. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"scraper/",
"scraper/client.py",
"scraper/parsers.py",
"scraper/storage.py"
],
"constraints": [
"avoid adding new dependencies",
"prefer explicit types and docstrings",
"k... | This is a feature-planning request for audit logging in a web scraping toolkit. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of audit logging in the web scraping toolkit.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"web_scraping_toolkit",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0154 | JumpLander Agent Dataset | 1.0 | feature_planning | python | testing utility package | medium | Extend the codebase to support multi-file upload while keeping the API stable. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"preserve current public API",
"support Python 3.10+",
"ensure tests are easy to run local... | This is a feature-planning request for multi-file upload in a testing utility package. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of multi-file upload in the testing utility package.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge ca... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0155 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | easy | Add rate limiting to the authentication module without breaking existing behavior. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"auth/",
"auth/jwt.py",
"auth/routes.py",
"auth/security.py"
],
"constraints": [
"ensure tests are easy to run locally",
"avoid adding new dependencies",
"support P... | This is a feature-planning request for rate limiting in a authentication module. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of rate limiting in the authentication module.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"authentication_module",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0156 | JumpLander Agent Dataset | 1.0 | feature_planning | python | background worker | easy | Introduce pagination with minimal changes and clear validation steps. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"worker/",
"worker/tasks.py",
"worker/scheduler.py",
"worker/queues.py"
],
"constraints": [
"ensure tests are easy to run locally",
"keep backward compatibility",
"support Python 3.10+"
... | This is a feature-planning request for pagination in a background worker. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of pagination in the background worker.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"Cal... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"background_worker",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0157 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | easy | Add audit logging to the Flask admin dashboard without breaking existing behavior. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"support Python 3.10+",
"ensure tests are easy to run locally",
"limit chan... | This is a feature-planning request for audit logging in a Flask admin dashboard. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of audit logging in the Flask admin dashboard.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"flask_admin_dashboard",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0158 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | easy | Design a clean way to support multi-file upload in the current Python project. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"api/",
"app/main.py",
"app/routes/auth.py",
"app/services/user_service.py"
],
"constraints": [
"preserve current public API",
"limit changes to 2-3 files when possible",
... | This is a feature-planning request for multi-file upload in a FastAPI service. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of multi-file upload in the FastAPI service.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"fastapi_service",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0159 | JumpLander Agent Dataset | 1.0 | feature_planning | python | data processing library | easy | Design a clean way to support background cleanup jobs in the current Python project. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"src/",
"src/pipeline.py",
"src/transformers.py",
"src/io.py"
],
"constraints": [
"support Python 3.10+",
"preserve current public API",
"avoid adding new dependencies"
]... | This is a feature-planning request for background cleanup jobs in a data processing library. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of background cleanup jobs in the data processing library.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important e... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"data_processing_library",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0160 | JumpLander Agent Dataset | 1.0 | feature_planning | python | web scraping toolkit | hard | Design a clean way to support JWT login in the current Python project. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"scraper/",
"scraper/client.py",
"scraper/parsers.py",
"scraper/storage.py"
],
"constraints": [
"keep response latency low",
"limit changes to 2-3 files when possible",
"avoid ad... | This is a feature-planning request for JWT login in a web scraping toolkit. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of JWT login in the web scraping toolkit.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"C... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"web_scraping_toolkit",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0161 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | medium | Add JWT login to the FastAPI service without breaking existing behavior. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"api/",
"app/main.py",
"app/routes/auth.py",
"app/services/user_service.py"
],
"constraints": [
"ensure tests are easy to run locally",
"limit changes to 2-3 files when possibl... | This is a feature-planning request for JWT login in a FastAPI service. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of JWT login in the FastAPI service.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"Call o... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"fastapi_service",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0162 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | hard | Introduce JWT login with minimal changes and clear validation steps. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"api/",
"app/main.py",
"app/routes/auth.py",
"app/services/user_service.py"
],
"constraints": [
"keep backward compatibility",
"avoid adding new dependencies",
"ens... | This is a feature-planning request for JWT login in a FastAPI service. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of JWT login in the FastAPI service.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"Call o... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"fastapi_service",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0163 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | hard | Add timezone-aware scheduling to the Flask admin dashboard without breaking existing behavior. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"prefer explicit types and docstrings",
"support Python 3.10+",
"preserve c... | This is a feature-planning request for timezone-aware scheduling in a Flask admin dashboard. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of timezone-aware scheduling in the Flask admin dashboard.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important e... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"flask_admin_dashboard",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0164 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | medium | Design a clean way to support audit logging in the current Python project. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"keep backward compatibility",
"ensure tests are easy to run locally",
"lim... | This is a feature-planning request for audit logging in a Flask admin dashboard. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of audit logging in the Flask admin dashboard.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"flask_admin_dashboard",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0165 | JumpLander Agent Dataset | 1.0 | feature_planning | python | testing utility package | hard | Add caching to the testing utility package without breaking existing behavior. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"keep backward compatibility",
"support Python 3.10+",
"limit changes to 2-3... | This is a feature-planning request for caching in a testing utility package. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of caching in the testing utility package.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0166 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | easy | Extend the codebase to support audit logging while keeping the API stable. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"avoid adding new dependencies",
"keep backward compatibility",
"preserve c... | This is a feature-planning request for audit logging in a Flask admin dashboard. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of audit logging in the Flask admin dashboard.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"flask_admin_dashboard",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0167 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | medium | Introduce JWT login with minimal changes and clear validation steps. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"ensure tests are easy to run locally",
"support Python 3.10+",
"keep respo... | This is a feature-planning request for JWT login in a Flask admin dashboard. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of JWT login in the Flask admin dashboard.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"flask_admin_dashboard",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0168 | JumpLander Agent Dataset | 1.0 | feature_planning | python | testing utility package | hard | Extend the codebase to support webhook delivery while keeping the API stable. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"avoid adding new dependencies",
"limit changes to 2-3 files when possible",
"ensure tests... | This is a feature-planning request for webhook delivery in a testing utility package. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of webhook delivery in the testing utility package.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cas... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0169 | JumpLander Agent Dataset | 1.0 | feature_planning | python | data processing library | medium | Extend the codebase to support search filters while keeping the API stable. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"src/",
"src/pipeline.py",
"src/transformers.py",
"src/io.py"
],
"constraints": [
"support Python 3.10+",
"prefer explicit types and docstrings",
"preserve current ... | This is a feature-planning request for search filters in a data processing library. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of search filters in the data processing library.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"data_processing_library",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0170 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | medium | Add timezone-aware scheduling to the authentication module without breaking existing behavior. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"auth/",
"auth/jwt.py",
"auth/routes.py",
"auth/security.py"
],
"constraints": [
"ensure tests are easy to run locally",
"support Python 3.10+",
"preserve current public API"
],
"notes... | This is a feature-planning request for timezone-aware scheduling in a authentication module. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of timezone-aware scheduling in the authentication module.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important e... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"authentication_module",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0171 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | medium | Extend the codebase to support caching while keeping the API stable. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"avoid adding new dependencies",
"keep backward compatibility",
"limit changes to 2-3 files when... | This is a feature-planning request for caching in a CLI automation tool. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of caching in the CLI automation tool.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"Call... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0172 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | hard | Introduce timezone-aware scheduling with minimal changes and clear validation steps. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"preserve current public API",
"keep response latency low",
"keep backward ... | This is a feature-planning request for timezone-aware scheduling in a Flask admin dashboard. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of timezone-aware scheduling in the Flask admin dashboard.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important e... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"flask_admin_dashboard",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0173 | JumpLander Agent Dataset | 1.0 | feature_planning | python | background worker | hard | Add caching to the background worker without breaking existing behavior. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"worker/",
"worker/tasks.py",
"worker/scheduler.py",
"worker/queues.py"
],
"constraints": [
"limit changes to 2-3 files when possible",
"preserve current public API",
... | This is a feature-planning request for caching in a background worker. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of caching in the background worker.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"Call o... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"background_worker",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0174 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | easy | Introduce rate limiting with minimal changes and clear validation steps. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"api/",
"app/main.py",
"app/routes/auth.py",
"app/services/user_service.py"
],
"constraints": [
"ensure tests are easy to run locally",
"keep backward compatibility",
"keep... | This is a feature-planning request for rate limiting in a FastAPI service. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of rate limiting in the FastAPI service.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"Ca... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"fastapi_service",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0175 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | hard | Extend the codebase to support caching while keeping the API stable. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"support Python 3.10+",
"limit changes to 2-3 files when possible",
"keep backward compatibility"
],
"... | This is a feature-planning request for caching in a CLI automation tool. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of caching in the CLI automation tool.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"Call... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0176 | JumpLander Agent Dataset | 1.0 | feature_planning | python | background worker | hard | Introduce pagination with minimal changes and clear validation steps. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"worker/",
"worker/tasks.py",
"worker/scheduler.py",
"worker/queues.py"
],
"constraints": [
"support Python 3.10+",
"limit changes to 2-3 files when possible",
"prefer expl... | This is a feature-planning request for pagination in a background worker. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of pagination in the background worker.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"Cal... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"background_worker",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0177 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | medium | Introduce background cleanup jobs with minimal changes and clear validation steps. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"api/",
"app/main.py",
"app/routes/auth.py",
"app/services/user_service.py"
],
"constraints": [
"keep backward compatibility",
"avoid adding new dependencies",
"preserve current public API... | This is a feature-planning request for background cleanup jobs in a FastAPI service. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of background cleanup jobs in the FastAPI service.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge case... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"fastapi_service",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0178 | JumpLander Agent Dataset | 1.0 | feature_planning | python | background worker | easy | Design a clean way to support CSV export in the current Python project. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"worker/",
"worker/tasks.py",
"worker/scheduler.py",
"worker/queues.py"
],
"constraints": [
"preserve current public API",
"keep response latency low",
"ensure test... | This is a feature-planning request for CSV export in a background worker. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of CSV export in the background worker.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"Cal... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"background_worker",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0179 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | medium | Add timezone-aware scheduling to the CLI automation tool without breaking existing behavior. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"avoid adding new dependencies",
"ensure tests are easy to run locally",
"keep response l... | This is a feature-planning request for timezone-aware scheduling in a CLI automation tool. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of timezone-aware scheduling in the CLI automation tool.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edg... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0180 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | hard | Introduce audit logging with minimal changes and clear validation steps. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"auth/",
"auth/jwt.py",
"auth/routes.py",
"auth/security.py"
],
"constraints": [
"preserve current public API",
"prefer explicit types and docstrings",
"limit changes to 2-3 files when pos... | This is a feature-planning request for audit logging in a authentication module. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of audit logging in the authentication module.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"authentication_module",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0181 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | hard | Design a clean way to support CSV export in the current Python project. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"preserve current public API",
"limit changes to 2-3 files when possible",
"keep ... | This is a feature-planning request for CSV export in a Flask admin dashboard. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of CSV export in the Flask admin dashboard.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"flask_admin_dashboard",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0182 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | medium | Extend the codebase to support rate limiting while keeping the API stable. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"limit changes to 2-3 files when possible",
"support Python 3.10+",
... | This is a feature-planning request for rate limiting in a Flask admin dashboard. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of rate limiting in the Flask admin dashboard.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"flask_admin_dashboard",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0183 | JumpLander Agent Dataset | 1.0 | feature_planning | python | web scraping toolkit | hard | Add async task retries to the web scraping toolkit without breaking existing behavior. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"scraper/",
"scraper/client.py",
"scraper/parsers.py",
"scraper/storage.py"
],
"constraints": [
"ensure tests are easy to run locally",
"support Python 3.10+",
"keep backward compatibility... | This is a feature-planning request for async task retries in a web scraping toolkit. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of async task retries in the web scraping toolkit.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge case... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"web_scraping_toolkit",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0184 | JumpLander Agent Dataset | 1.0 | feature_planning | python | testing utility package | easy | Introduce webhook delivery with minimal changes and clear validation steps. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"keep backward compatibility",
"avoid adding new dependencies",
"support Python 3.10... | This is a feature-planning request for webhook delivery in a testing utility package. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of webhook delivery in the testing utility package.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cas... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0185 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | medium | Introduce async task retries with minimal changes and clear validation steps. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"api/",
"app/main.py",
"app/routes/auth.py",
"app/services/user_service.py"
],
"constraints": [
"support Python 3.10+",
"limit changes to 2-3 files when possible",
"avoid adding new depend... | This is a feature-planning request for async task retries in a FastAPI service. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of async task retries in the FastAPI service.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"fastapi_service",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0186 | JumpLander Agent Dataset | 1.0 | feature_planning | python | background worker | easy | Add pagination to the background worker without breaking existing behavior. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"worker/",
"worker/tasks.py",
"worker/scheduler.py",
"worker/queues.py"
],
"constraints": [
"prefer explicit types and docstrings",
"ensure tests are easy to run locally",
... | This is a feature-planning request for pagination in a background worker. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of pagination in the background worker.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"Cal... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"background_worker",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0187 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | medium | Design a clean way to support webhook delivery in the current Python project. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"auth/",
"auth/jwt.py",
"auth/routes.py",
"auth/security.py"
],
"constraints": [
"ensure tests are easy to run locally",
"keep backward compatibility",
"support Python 3.10+"
]... | This is a feature-planning request for webhook delivery in a authentication module. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of webhook delivery in the authentication module.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"authentication_module",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0188 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | medium | Add audit logging to the FastAPI service without breaking existing behavior. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"api/",
"app/main.py",
"app/routes/auth.py",
"app/services/user_service.py"
],
"constraints": [
"ensure tests are easy to run locally",
"keep response latency low",
"suppor... | This is a feature-planning request for audit logging in a FastAPI service. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of audit logging in the FastAPI service.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"Ca... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"fastapi_service",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0189 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | hard | Add rate limiting to the authentication module without breaking existing behavior. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"auth/",
"auth/jwt.py",
"auth/routes.py",
"auth/security.py"
],
"constraints": [
"limit changes to 2-3 files when possible",
"keep backward compatibility",
"preserve curre... | This is a feature-planning request for rate limiting in a authentication module. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of rate limiting in the authentication module.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"authentication_module",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0190 | JumpLander Agent Dataset | 1.0 | feature_planning | python | testing utility package | medium | Introduce timezone-aware scheduling with minimal changes and clear validation steps. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"avoid adding new dependencies",
"support Python 3.10+",
"keep backward compatibili... | This is a feature-planning request for timezone-aware scheduling in a testing utility package. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of timezone-aware scheduling in the testing utility package.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0191 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | easy | Add webhook delivery to the authentication module without breaking existing behavior. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"auth/",
"auth/jwt.py",
"auth/routes.py",
"auth/security.py"
],
"constraints": [
"limit changes to 2-3 files when possible",
"prefer explicit types and docstrings",
"preserve current publi... | This is a feature-planning request for webhook delivery in a authentication module. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of webhook delivery in the authentication module.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"authentication_module",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0192 | JumpLander Agent Dataset | 1.0 | feature_planning | python | background worker | medium | Add JWT login to the background worker without breaking existing behavior. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"worker/",
"worker/tasks.py",
"worker/scheduler.py",
"worker/queues.py"
],
"constraints": [
"avoid adding new dependencies",
"keep response latency low",
"limit changes to... | This is a feature-planning request for JWT login in a background worker. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of JWT login in the background worker.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"Call... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"background_worker",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0193 | JumpLander Agent Dataset | 1.0 | feature_planning | python | background worker | easy | Design a clean way to support timezone-aware scheduling in the current Python project. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"worker/",
"worker/tasks.py",
"worker/scheduler.py",
"worker/queues.py"
],
"constraints": [
"support Python 3.10+",
"keep backward compatibility",
"avoid adding new dependencies"
],
"n... | This is a feature-planning request for timezone-aware scheduling in a background worker. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of timezone-aware scheduling in the background worker.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge ... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"background_worker",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0194 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | medium | Design a clean way to support background cleanup jobs in the current Python project. | {
"project_summary": "A scraping-oriented project that collects public data and stores normalized results.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"avoid adding new dependencies",
"prefer explicit types and docstrings",
"ensure t... | This is a feature-planning request for background cleanup jobs in a CLI automation tool. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of background cleanup jobs in the CLI automation tool.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge ... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"cli_automation_tool",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0195 | JumpLander Agent Dataset | 1.0 | feature_planning | python | testing utility package | medium | Introduce caching with minimal changes and clear validation steps. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"ensure tests are easy to run locally",
"avoid adding new dependencies",
"support Python 3... | This is a feature-planning request for caching in a testing utility package. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of caching in the testing utility package.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0196 | JumpLander Agent Dataset | 1.0 | feature_planning | python | testing utility package | hard | Introduce caching with minimal changes and clear validation steps. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"keep response latency low",
"prefer explicit types and docstrings",
"keep backward compatibility"
... | This is a feature-planning request for caching in a testing utility package. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of caching in the testing utility package.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"testing_utility_package",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0197 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | medium | Extend the codebase to support rate limiting while keeping the API stable. | {
"project_summary": "A CLI tool used to automate repetitive developer operations.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"prefer explicit types and docstrings",
"keep backward compatibility",
"limit changes to 2-... | This is a feature-planning request for rate limiting in a Flask admin dashboard. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of rate limiting in the Flask admin dashboard.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"flask_admin_dashboard",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0198 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | hard | Add caching to the Flask admin dashboard without breaking existing behavior. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"limit changes to 2-3 files when possible",
"support Python 3.10+",
"keep r... | This is a feature-planning request for caching in a Flask admin dashboard. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of caching in the Flask admin dashboard.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"Ca... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"flask_admin_dashboard",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0199 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | easy | Design a clean way to support audit logging in the current Python project. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"api/",
"app/main.py",
"app/routes/auth.py",
"app/services/user_service.py"
],
"constraints": [
"ensure tests are easy to run locally",
"keep response latency low",
"suppor... | This is a feature-planning request for audit logging in a FastAPI service. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of audit logging in the FastAPI service.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"Ca... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"fastapi_service",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
jlv1_0200 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | hard | Add audit logging to the FastAPI service without breaking existing behavior. | {
"project_summary": "A background-worker application that processes queued jobs and emits events.",
"files": [
"api/",
"app/main.py",
"app/routes/auth.py",
"app/services/user_service.py"
],
"constraints": [
"ensure tests are easy to run locally",
"prefer explicit types and docstrings",
... | This is a feature-planning request for audit logging in a FastAPI service. The best answer should first map the feature to the existing architecture, then propose a minimal implementation path, and finally define the validation plan. | [
"Clarify the exact scope of audit logging in the FastAPI service.",
"Inspect the existing modules that already handle request flow, validation, and persistence.",
"Propose the smallest set of changes that introduces the feature safely.",
"Define tests for the new behavior and the important edge cases.",
"Ca... | {
"style": "structured, concise, developer-focused",
"must_include": [
"clear reasoning",
"actionable next steps",
"risk or edge-case notes",
"validation suggestion"
]
} | [
"understand the request",
"identify the relevant files or signals",
"explain the reasoning",
"propose a safe next step",
"highlight verification"
] | [
"feature_planning",
"fastapi_service",
"agent_planning",
"python"
] | {
"source": "synthetic_jump_lander_v1",
"created_on": "2026-06-05T00:00:00",
"license": "CC BY 4.0"
} | null | null | null |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.