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_0001 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | hard | Introduce CSV export with minimal changes and clear validation steps. | {
"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": [
"support Python 3.10+",
"avoid adding new dependencies",
"limit changes to 2-3 fi... | 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_0002 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | easy | 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": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"keep backward compatibility",
"prefer explicit types and docstrings",
"li... | This is a feature-planning request for background cleanup jobs 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 background cleanup jobs 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 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",
"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_0003 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | medium | Design a clean way to support webhook delivery 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": [
"limit changes to 2-3 files when possible",
"avoid adding new dependencies",
... | This is a feature-planning request for webhook delivery 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 webhook delivery 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_0004 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | medium | Extend the codebase to support JWT login while keeping the API stable. | {
"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": [
"ensure tests are easy to run locally",
"preserve current public API",
"avo... | 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_0005 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | medium | Extend the codebase to support pagination 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",
"preserve current public API",
"limit chan... | 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_0006 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | medium | Extend the codebase to support timezone-aware scheduling while keeping the API stable. | {
"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": [
"avoid adding new dependencies",
"support Python 3.10+",
"keep backward comp... | This is a feature-planning request for timezone-aware scheduling 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 timezone-aware scheduling 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 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_0007 | JumpLander Agent Dataset | 1.0 | feature_planning | python | background worker | 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": [
"worker/",
"worker/tasks.py",
"worker/scheduler.py",
"worker/queues.py"
],
"constraints": [
"avoid adding new dependencies",
"keep backward compatibility",
"ensure tests a... | 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_0008 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | easy | Add async task retries 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": [
"limit changes to 2-3 files when possible",
"preserve current public API",
"support Python ... | This is a feature-planning request for async task retries 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 async task retries 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 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",
"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_0009 | JumpLander Agent Dataset | 1.0 | feature_planning | python | background worker | hard | Design a clean way to support multi-file upload in the current Python project. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"worker/",
"worker/tasks.py",
"worker/scheduler.py",
"worker/queues.py"
],
"constraints": [
"keep response latency low",
"ensure tests are easy to run locally",
"limit changes to... | 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_0010 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | hard | Design a clean way to support webhook delivery in the current Python project. | {
"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",
"support Python 3.10+",
"limit changes to 2-3 files when possible"
],
"... | This is a feature-planning request for webhook delivery 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 webhook delivery 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_0011 | JumpLander Agent Dataset | 1.0 | feature_planning | python | data processing library | medium | Introduce caching 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 backward compatibility",
"avoid adding new dependencies",
"prefer explicit types and docstrings"
]... | This is a feature-planning request for caching 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 caching 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_0012 | JumpLander Agent Dataset | 1.0 | feature_planning | python | web scraping toolkit | medium | Design a clean way to support pagination in the current Python project. | {
"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": [
"ensure tests are easy to run locally",
"avoid adding new dependencies",... | This is a feature-planning request for pagination 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 pagination 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_0013 | JumpLander Agent Dataset | 1.0 | feature_planning | python | testing utility package | hard | Introduce JWT login 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": [
"preserve current public API",
"avoid adding new dependencies",
"ensure tests are ea... | 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_0014 | 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 utility package that wraps common data transformation and validation tasks.",
"files": [
"scraper/",
"scraper/client.py",
"scraper/parsers.py",
"scraper/storage.py"
],
"constraints": [
"limit changes to 2-3 files when possible",
"preserve current public API",
... | 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_0015 | JumpLander Agent Dataset | 1.0 | feature_planning | python | testing utility package | hard | Add pagination to the testing utility package without breaking existing behavior. | {
"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",
"prefer explicit types and docstrings",
"ensure te... | 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_0016 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | hard | Add background cleanup jobs 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": [
"limit changes to 2-3 files when possible",
"support Python 3.10+",
"keep response ... | 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_0017 | JumpLander Agent Dataset | 1.0 | feature_planning | python | web scraping toolkit | hard | Add webhook delivery 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": [
"avoid adding new dependencies",
"ensure tests are easy to run locally",
"keep response late... | This is a feature-planning request for webhook delivery 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 webhook delivery 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_0018 | JumpLander Agent Dataset | 1.0 | feature_planning | python | background worker | hard | Introduce pagination with minimal changes and clear validation steps. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"worker/",
"worker/tasks.py",
"worker/scheduler.py",
"worker/queues.py"
],
"constraints": [
"limit changes to 2-3 files when possible",
"avoid adding new dependencies",
"support ... | 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_0019 | JumpLander Agent Dataset | 1.0 | feature_planning | python | web scraping toolkit | hard | Design a clean way to support webhook delivery in the current Python project. | {
"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",
"limit changes to 2-3 files when possible",
"ensure tests a... | This is a feature-planning request for webhook delivery 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 webhook delivery 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_0020 | JumpLander Agent Dataset | 1.0 | feature_planning | python | data processing library | hard | Introduce JWT login with minimal changes and clear validation steps. | {
"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",
"keep response latency low",
"limit changes to 2-3 files when pos... | 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_0021 | JumpLander Agent Dataset | 1.0 | feature_planning | python | background worker | easy | Add audit logging 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",
"preserve current public API",
"limit changes ... | This is a feature-planning request for audit logging 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 audit logging 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_0022 | JumpLander Agent Dataset | 1.0 | feature_planning | python | data processing library | hard | Add background cleanup jobs 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": [
"avoid adding new dependencies",
"ensure tests are easy to run locally",
"support Python 3.10+"
... | 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_0023 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | medium | 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": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"preserve current public API",
"prefer explicit types and docstrings",
"keep response late... | This is a feature-planning request for JWT login 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 JWT login 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.",
"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",
"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_0024 | JumpLander Agent Dataset | 1.0 | feature_planning | python | data processing library | medium | Design a clean way to support webhook delivery in the current Python project. | {
"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",
"support Python 3.10+",
"ensure tests are easy to run locally"
],
"notes"... | 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_0025 | JumpLander Agent Dataset | 1.0 | feature_planning | python | testing utility package | hard | Design a clean way to support pagination in the current Python project. | {
"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": [
"support Python 3.10+",
"keep backward compatibility",
"preserve current public API"
],
... | 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_0026 | 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 small Python service that exposes REST endpoints for user workflows.",
"files": [
"src/",
"src/pipeline.py",
"src/transformers.py",
"src/io.py"
],
"constraints": [
"keep backward compatibility",
"prefer explicit types and docstrings",
"ensure tests are easy to... | 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_0027 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | hard | Introduce CSV export 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": [
"avoid adding new dependencies",
"keep response latency low",
"prefer explicit types and do... | 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_0028 | JumpLander Agent Dataset | 1.0 | feature_planning | python | testing utility package | easy | Design a clean way to support async task retries in the current Python project. | {
"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": [
"prefer explicit types and docstrings",
"avoid adding new dependencies",
"su... | This is a feature-planning request for async task retries 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 async task retries 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 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",
"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_0029 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | 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": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"ensure tests are easy to run locally",
"support Python 3.10+",
"li... | 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_0030 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | easy | Add caching 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": [
"keep backward compatibility",
"support Python 3.10+",
"ensure tests are easy to run locally... | This is a feature-planning request for caching 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 caching 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 out... | {
"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_0031 | JumpLander Agent Dataset | 1.0 | feature_planning | python | data processing library | medium | Design a clean way to support async task retries in the current Python project. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"src/",
"src/pipeline.py",
"src/transformers.py",
"src/io.py"
],
"constraints": [
"prefer explicit types and docstrings",
"avoid adding new dependencies",
"support Python ... | This is a feature-planning request for async task retries 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 async task retries 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 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",
"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_0032 | JumpLander Agent Dataset | 1.0 | feature_planning | python | testing utility package | easy | Add async task retries to the testing utility package without breaking existing behavior. | {
"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": [
"prefer explicit types and docstrings",
"limit changes to 2-3 files when possible",
"keep ... | This is a feature-planning request for async task retries 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 async task retries 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 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",
"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_0033 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | easy | Design a clean way to support pagination in the current Python project. | {
"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": [
"preserve current public API",
"support Python 3.10+",
"limit change... | This is a feature-planning request for pagination 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 pagination 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 ... | {
"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_0034 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | medium | Design a clean way to support CSV export 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": [
"limit changes to 2-3 files when possible",
"keep backward compatibility",
"support Python 3.10+"
],
"n... | This is a feature-planning request for CSV export 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 CSV export 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_0035 | 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 utility package that wraps common data transformation and validation tasks.",
"files": [
"scraper/",
"scraper/client.py",
"scraper/parsers.py",
"scraper/storage.py"
],
"constraints": [
"preserve current public API",
"avoid adding new dependencies",
"prefer exp... | 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_0036 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | hard | Introduce timezone-aware scheduling 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",
"prefer explicit types and docstrings",
... | This is a feature-planning request for timezone-aware scheduling 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 timezone-aware scheduling 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 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_0037 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | hard | Add CSV export 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": [
"preserve current public API",
"keep backward compatibility",
"keep response latency low"
],
... | This is a feature-planning request for CSV export 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 CSV export 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_0038 | JumpLander Agent Dataset | 1.0 | feature_planning | python | data processing library | hard | Add search filters 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": [
"support Python 3.10+",
"keep response latency low",
"limit changes to 2-3 files when possible"
... | 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_0039 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | easy | Introduce search filters 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",
"avoid adding new dependencies",
"ensure tests are easy to run... | 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_0040 | JumpLander Agent Dataset | 1.0 | feature_planning | python | web scraping toolkit | easy | Design a clean way to support search filters 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",
"support Python 3.10+",
"preserve current public API"... | 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_0041 | JumpLander Agent Dataset | 1.0 | feature_planning | python | testing utility package | medium | Add background cleanup jobs to the testing utility package without breaking existing behavior. | {
"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": [
"avoid adding new dependencies",
"keep response latency low",
"prefer explicit types... | This is a feature-planning request for background cleanup jobs 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 background cleanup jobs 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 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",
"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_0042 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | medium | Add multi-file upload 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": [
"support Python 3.10+",
"preserve current public API",
"limit changes to 2-3 files when p... | This is a feature-planning request for multi-file upload 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 multi-file upload 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_0043 | 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": [
"keep response latency low",
"ensure tests are easy to run locally",
"keep ... | 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_0044 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | hard | Design a clean way to support pagination 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": [
"keep response latency low",
"preserve current public API",
"prefer explic... | 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_0045 | JumpLander Agent Dataset | 1.0 | feature_planning | python | background worker | hard | Introduce async task retries with minimal changes and clear validation steps. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"worker/",
"worker/tasks.py",
"worker/scheduler.py",
"worker/queues.py"
],
"constraints": [
"prefer explicit types and docstrings",
"preserve current public API",
"keep backward ... | This is a feature-planning request for async task retries 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 async task retries 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_0046 | 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 CLI tool used to automate repetitive developer operations.",
"files": [
"auth/",
"auth/jwt.py",
"auth/routes.py",
"auth/security.py"
],
"constraints": [
"keep backward compatibility",
"preserve current public API",
"avoid adding new dependencies"
],
"notes... | 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_0047 | 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 utility package that wraps common data transformation and validation tasks.",
"files": [
"tests/",
"tests/test_api.py",
"tests/test_utils.py",
"conftest.py"
],
"constraints": [
"keep backward compatibility",
"prefer explicit types and docstrings",
"limit chang... | 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_0048 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | medium | Design a clean way to support multi-file upload in the current Python project. | {
"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": [
"limit changes to 2-3 files when possible",
"avoid adding new dependencies",
"keep backward ... | 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_0049 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | hard | Design a clean way to support multi-file upload in the current Python project. | {
"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",
"keep backward compatibility... | 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_0050 | 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": [
"support Python 3.10+",
"limit changes to 2-3 files when possible",
"avoid adding new depe... | 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_0051 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | medium | Introduce JWT login with minimal changes and clear validation steps. | {
"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": [
"limit changes to 2-3 files when possible",
"prefer explicit types and docstrin... | 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_0052 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | easy | Add timezone-aware scheduling to the CLI automation tool without breaking existing behavior. | {
"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": [
"limit changes to 2-3 files when possible",
"prefer explicit types and docstrings",
... | 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_0053 | JumpLander Agent Dataset | 1.0 | feature_planning | python | data processing library | easy | Introduce audit logging with minimal changes and clear validation steps. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"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 ne... | 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_0054 | JumpLander Agent Dataset | 1.0 | feature_planning | python | data processing library | medium | Introduce search filters 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",
"keep backward compatibility"
]... | 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_0055 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | hard | Introduce caching with minimal changes and clear validation steps. | {
"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": [
"keep backward compatibility",
"prefer explicit types and docstrings",
"preserve current p... | This is a feature-planning request for caching 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 caching 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.",
"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",
"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_0056 | JumpLander Agent Dataset | 1.0 | feature_planning | python | web scraping toolkit | medium | Add CSV export 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": [
"limit changes to 2-3 files when possible",
"preserve current public API",
"ensure tests are... | 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_0057 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | easy | Design a clean way to support search filters in the current Python project. | {
"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": [
"keep response latency low",
"keep backward compatibility",
"ensure... | 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_0058 | JumpLander Agent Dataset | 1.0 | feature_planning | python | data processing library | medium | Extend the codebase to support multi-file upload 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": [
"avoid adding new dependencies",
"ensure tests are easy to run locally",
"preserve current... | This is a feature-planning request for multi-file upload 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 multi-file upload 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 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",
"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_0059 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | medium | Introduce timezone-aware scheduling 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",
"ensure tests are easy to run locally",
"support Python 3.10+"... | 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_0060 | JumpLander Agent Dataset | 1.0 | feature_planning | python | web scraping toolkit | hard | Design a clean way to support webhook delivery in the current Python project. | {
"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": [
"support Python 3.10+",
"prefer explicit types and docstrings",
"ens... | This is a feature-planning request for webhook delivery 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 webhook delivery 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_0061 | 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 CLI tool used to automate repetitive developer operations.",
"files": [
"cli/",
"cli/__main__.py",
"cli/commands.py",
"cli/config.py"
],
"constraints": [
"limit changes to 2-3 files when possible",
"keep response latency low",
"keep backward compatibility"
]... | 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_0062 | JumpLander Agent Dataset | 1.0 | feature_planning | python | data processing library | hard | Introduce search filters with minimal changes and clear validation steps. | {
"project_summary": "A utility package that wraps common data transformation and validation tasks.",
"files": [
"src/",
"src/pipeline.py",
"src/transformers.py",
"src/io.py"
],
"constraints": [
"prefer explicit types and docstrings",
"support Python 3.10+",
"limit changes to 2-3 fil... | 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_0063 | JumpLander Agent Dataset | 1.0 | feature_planning | python | testing utility package | medium | Design a clean way to support timezone-aware scheduling in the current Python project. | {
"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": [
"avoid adding new dependencies",
"preserve current public API",
"keep response laten... | 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_0064 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | easy | Introduce async task retries with minimal changes and clear validation steps. | {
"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": [
"support Python 3.10+",
"limit changes to 2-3 files when possible",
"avoid... | This is a feature-planning request for async task retries 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 async task retries 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 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",
"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_0065 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | easy | Extend the codebase to support async task retries while keeping the API stable. | {
"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": [
"avoid adding new dependencies",
"support Python 3.10+",
"limit changes to 2... | 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_0066 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | easy | Extend the codebase to support audit logging while keeping the API stable. | {
"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": [
"support Python 3.10+",
"avoid adding new dependencies",
"ensure tests are easy to run locally"
... | 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_0067 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | easy | Design a clean way to support async task retries 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 backward compatibility",
"keep response late... | 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_0068 | 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": [
"ensure tests are easy to run locally",
"limit changes to 2-3 files when possible",
... | 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_0069 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | medium | Extend the codebase to support webhook delivery while keeping the API stable. | {
"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": [
"preserve current public API",
"ensure tests are easy to run locally",
"support Pyt... | 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_0070 | JumpLander Agent Dataset | 1.0 | feature_planning | python | data processing library | medium | Introduce caching 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": [
"prefer explicit types and docstrings",
"ensure tests are easy to run locally",
"avoid adding new dependen... | This is a feature-planning request for caching 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 caching 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_0071 | 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 CLI tool used to automate repetitive developer operations.",
"files": [
"dashboard/",
"dashboard/app.py",
"dashboard/views.py",
"dashboard/utils.py"
],
"constraints": [
"support Python 3.10+",
"preserve current public API",
"limit changes to 2-3 files when pos... | 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_0072 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | hard | 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": [
"support Python 3.10+",
"prefer explicit types and docstrings",
"ensure te... | 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_0073 | JumpLander Agent Dataset | 1.0 | feature_planning | python | data processing library | medium | 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": [
"src/",
"src/pipeline.py",
"src/transformers.py",
"src/io.py"
],
"constraints": [
"limit changes to 2-3 files when possible",
"preserve current public API",
"keep r... | This is a feature-planning request for pagination 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 pagination 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_0074 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | hard | Extend the codebase to support async task retries while keeping the API stable. | {
"project_summary": "A small Python service that exposes REST endpoints for user workflows.",
"files": [
"api/",
"app/main.py",
"app/routes/auth.py",
"app/services/user_service.py"
],
"constraints": [
"limit changes to 2-3 files when possible",
"prefer explicit types and docstrings",
... | 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_0075 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | hard | Add audit logging 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",
"preserve current public API",
"support Pyt... | 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_0076 | JumpLander Agent Dataset | 1.0 | feature_planning | python | data processing library | medium | Design a clean way to support audit logging in the current Python project. | {
"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": [
"keep response latency low",
"support Python 3.10+",
"limit changes to 2-3 files when possible"
... | 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_0077 | JumpLander Agent Dataset | 1.0 | feature_planning | python | background worker | hard | Extend the codebase to support caching 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": [
"preserve current public API",
"limit changes to 2-3 files when possible",
"sup... | 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_0078 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | medium | Add search filters to the FastAPI service without breaking existing behavior. | {
"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": [
"avoid adding new dependencies",
"ensure tests are easy to run locally",
"s... | This is a feature-planning request for search filters 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 search filters 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.",
"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",
"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_0079 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | medium | Introduce CSV export with minimal changes and clear validation steps. | {
"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": [
"limit changes to 2-3 files when possible",
"preserve current public API",
"avoid ... | This is a feature-planning request for CSV export 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 CSV export 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_0080 | JumpLander Agent Dataset | 1.0 | feature_planning | python | background worker | easy | Introduce search filters with minimal changes and clear validation steps. | {
"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 search filters 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 search filters 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_0081 | 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 small Python service that exposes REST endpoints for user workflows.",
"files": [
"api/",
"app/main.py",
"app/routes/auth.py",
"app/services/user_service.py"
],
"constraints": [
"avoid adding new dependencies",
"limit changes to 2-3 files when possible",
"ensu... | 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_0082 | JumpLander Agent Dataset | 1.0 | feature_planning | python | data processing library | hard | Add async task retries 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": [
"preserve current public API",
"avoid adding new dependencies",
"limit changes to ... | This is a feature-planning request for async task retries 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 async task retries 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 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",
"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_0083 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | easy | Design a clean way to support background cleanup jobs in the current Python project. | {
"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",
"ensure tests are easy to run locally",
"preserve c... | This is a feature-planning request for background cleanup jobs 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 background cleanup jobs 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 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",
"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_0084 | JumpLander Agent Dataset | 1.0 | feature_planning | python | Flask admin dashboard | hard | Introduce JWT login 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": [
"avoid adding new dependencies",
"keep response latency low",
"keep backward compatibility"... | 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_0085 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | easy | Design a clean way to support search filters 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": [
"avoid adding new dependencies",
"keep response latency low",
"ensure tests are easy to ru... | This is a feature-planning request for search filters 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 search filters 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_0086 | JumpLander Agent Dataset | 1.0 | feature_planning | python | web scraping toolkit | hard | Add caching 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": [
"keep backward compatibility",
"preserve current public API",
"keep ... | This is a feature-planning request for caching 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 caching 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.",
"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",
"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_0087 | JumpLander Agent Dataset | 1.0 | feature_planning | python | background worker | easy | Introduce pagination with minimal changes and clear validation steps. | {
"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": [
"keep backward compatibility",
"limit changes to 2-3 files when possible",
... | 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_0088 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | hard | Extend the codebase to support multi-file upload while keeping the API stable. | {
"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": [
"preserve current public API",
"support Python 3.10+",
"avoid adding new dependencies"
],... | This is a feature-planning request for multi-file upload 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 multi-file upload 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 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",
"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_0089 | JumpLander Agent Dataset | 1.0 | feature_planning | python | web scraping toolkit | medium | Extend the codebase to support background cleanup jobs 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",
"support Python 3.10+",
"ensure test... | 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_0090 | JumpLander Agent Dataset | 1.0 | feature_planning | python | background worker | hard | Add async task retries 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": [
"keep response latency low",
"support Python 3.10+",
"avoid adding new d... | This is a feature-planning request for async task retries 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 async task retries 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_0091 | JumpLander Agent Dataset | 1.0 | feature_planning | python | authentication module | medium | Add multi-file upload 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": [
"prefer explicit types and docstrings",
"limit changes to 2-3 files when possible",
"prese... | This is a feature-planning request for multi-file upload 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 multi-file upload 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 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",
"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_0092 | JumpLander Agent Dataset | 1.0 | feature_planning | python | data processing library | hard | Introduce multi-file upload 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": [
"ensure tests are easy to run locally",
"preserve current public API",
"keep response latency low"
],
... | This is a feature-planning request for multi-file upload 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 multi-file upload 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 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",
"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_0093 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | medium | Design a clean way to support webhook delivery in the current Python project. | {
"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": [
"avoid adding new dependencies",
"prefer explicit types and docstrings",... | This is a feature-planning request for webhook delivery 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 webhook delivery 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_0094 | JumpLander Agent Dataset | 1.0 | feature_planning | python | data processing library | medium | Extend the codebase to support timezone-aware scheduling 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": [
"prefer explicit types and docstrings",
"support Python 3.10+",
"keep backward compatibility"
... | This is a feature-planning request for timezone-aware scheduling 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 timezone-aware scheduling 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... | {
"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_0095 | JumpLander Agent Dataset | 1.0 | feature_planning | python | data processing library | medium | Design a clean way to support search filters in the current Python project. | {
"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",
"ensure tests are easy to run locally",
"prefer explicit types and docstrings... | 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_0096 | JumpLander Agent Dataset | 1.0 | feature_planning | python | background worker | medium | Introduce search filters 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",
"prefer explicit types and docstrings",
"support Python ... | This is a feature-planning request for search filters 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 search filters 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_0097 | 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 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+",
"preserve current public API",
"keep backward compat... | 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_0098 | JumpLander Agent Dataset | 1.0 | feature_planning | python | CLI automation tool | hard | Design a clean way to support async task retries in the current Python project. | {
"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",
"preserve current public API",
"ensure tests are e... | This is a feature-planning request for async task retries 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 async task retries 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_0099 | JumpLander Agent Dataset | 1.0 | feature_planning | python | web scraping toolkit | medium | Design a clean way to support pagination in the current Python project. | {
"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": [
"keep response latency low",
"avoid adding new dependencies",
"preserve cur... | This is a feature-planning request for pagination 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 pagination 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_0100 | JumpLander Agent Dataset | 1.0 | feature_planning | python | FastAPI service | medium | Design a clean way to support timezone-aware scheduling 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": [
"keep response latency low",
"keep backward compatibility",
"limit changes t... | This is a feature-planning request for timezone-aware scheduling 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 timezone-aware scheduling 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 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 |
End of preview. Expand in Data Studio
Developed by JumpLander
AI Platform for Coding Agents, Software Engineering, and Intelligent Development Workflows
Deep Overview
JumpTrace-1K is not a traditional code-generation dataset.
Most programming datasets focus on transforming a prompt directly into code. While this approach can improve code completion capabilities, it does not adequately train models to behave like software engineering agents that must understand context, reason about a project, and make informed decisions before implementing changes.
JumpTrace-1K was designed to address that gap.
The dataset focuses on the intermediate reasoning process that occurs between receiving a request and producing a solution. Each sample encourages the model to identify relevant information, analyze project constraints, construct an implementation strategy, and describe validation procedures.
As a result, the dataset is particularly suitable for training and evaluating systems that perform:
- Repository understanding
- Engineering planning
- Bug investigation
- Code review reasoning
- Agent-style software development workflows
Rather than rewarding immediate code synthesis, the dataset promotes structured problem solving.
Design Philosophy
The core philosophy behind JumpTrace-1K is that effective coding agents should behave more like experienced engineers than autocomplete systems.
A strong engineering assistant should be able to:
- Understand the user's request.
- Identify relevant project components.
- Analyze constraints and risks.
- Create an implementation plan.
- Explain tradeoffs.
- Define validation steps.
- Produce a clear and actionable response.
These behaviors are explicitly represented in the dataset structure.
Dataset Structure
Each sample follows a consistent schema designed for agent-oriented training.
The dataset includes:
- A software engineering request.
- Project-level context.
- Structured analysis.
- Step-by-step planning.
- Expected response characteristics.
- Target behaviors for evaluation.
This format allows researchers to train models that learn not only what to do, but also how to reason about what should be done.
Intended Use Cases
JumpTrace-1K can be used for:
Supervised Fine-Tuning (SFT)
Training models to produce structured engineering reasoning and planning outputs.
Agent Evaluation
Measuring how effectively an AI system can understand repositories, identify relevant context, and propose implementation strategies.
Prompt Engineering Research
Studying how different prompts influence planning quality, reasoning depth, and task completion behavior.
Benchmark Development
Creating evaluation suites for engineering assistants, coding agents, and repository-aware systems.
Educational Applications
Teaching structured software engineering workflows and problem decomposition techniques.
What Makes This Dataset Different
Several characteristics distinguish JumpTrace-1K from conventional coding datasets:
Structured Reasoning
Every sample contains an explicit reasoning phase rather than only an input-output pair.
Planning-Oriented Design
The dataset rewards planning quality and implementation strategy formulation.
Repository Awareness
Tasks encourage understanding of project structure and contextual information.
Agent-Centric Workflows
The dataset reflects workflows commonly performed by modern coding agents and AI software assistants.
Consistent Formatting
A unified schema enables straightforward training, evaluation, filtering, and benchmarking.
Future Roadmap
Version 1.0 intentionally focuses on clean synthetic data with a controlled structure.
Future releases may introduce:
- Real-world repository contexts
- Multi-file code examples
- Pull request discussions
- GitHub issue threads
- Stack traces and debugging logs
- Test execution outputs
- Architecture diagrams
- Harder reasoning chains
- Multi-step agent trajectories
The goal is to gradually evolve JumpTrace into a comprehensive benchmark and training resource for next-generation software engineering agents.
Research Motivation
Recent advances in AI coding systems have demonstrated that software engineering performance depends on much more than code generation.
High-performing agents must understand context, plan actions, evaluate alternatives, and verify outcomes.
JumpTrace-1K was created to support research in these capabilities by providing a structured dataset that emphasizes reasoning, planning, and repository-level understanding.
The dataset serves as a foundation for experiments involving:
- Agentic AI systems
- Software engineering assistants
- Repository-aware language models
- Structured reasoning models
- Planning-focused fine-tuning
- Engineering workflow automation
By focusing on the reasoning process rather than only the final answer, JumpTrace-1K aims to support the development of more capable and reliable coding agents.
About JumpLander
JumpTrace-1K is part of the JumpLander ecosystem.
JumpLander is an AI platform focused on coding agents, software engineering workflows, repository intelligence, and developer-focused artificial intelligence tools.
- Website: https://jumplander.org
- Dataset Author: JumpLander
- Release: JumpTrace-1K v1.0
- License: CC BY 4.0
Learn more at: https://jumplander.org
- Downloads last month
- -