vibecodeit

Build Asana

KINDAreplaces $13.49/mosaves $161.88/yrback to the verdict

0%0 of 19 items done

Saved on this device only. Tick prerequisites first, then work the phases in order · do not start one until the checks above it pass.

Build a small project planner with dependency-aware milestones.

estimated effort multi-daythe files for this build are in the project pack

RuntimePython 3.12+ and FlaskStorageSQLite through Python sqlite3InterfaceJinja HTML templates, CSS and vanilla JavaScriptVerificationPython unittest and browser acceptance fixtures

Before step 1

Everything below is assumed from the first step. Tick each one when you actually have it, not when you plan to.

  1. installPython is free; this local prototype requires no hosting subscription.

    Why The local backend, tests and storage use Python.

    Get it Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. open ↗

    Verify python --version reports 3.12+ and python -c "import sqlite3" succeeds.

  2. installNo paid service required for this local step.

    Why You need to view the local interface and edit generated project files.

    Get it Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository.

    Verify You can create a text file in the project folder and open browser developer tools.

  3. have readyNo paid service required for this local step.

    Why This fixture makes the first end-to-end check reproducible.

    Get it Create synthetic sample data before implementation: Launch project: Draft blocks Review; Review blocks Publish; milestone on Friday. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records.

    Verify The fixture files and expected outcomes exist and can be inspected without a vendor account.

  4. decideNo paid service required for this local step.

    Why The full commercial product is larger than this guide.

    Get it The deliverable is a small project planner with dependency-aware milestones. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first.

    Verify You can name the primary workflow and the vendor features this version deliberately leaves out.

Data model

Create these before the first phase that stores anything. Changing a table later is the expensive kind of change.

- projects(id,name)
- tasks(id,project_id,title,owner,due_date,status,revision)
- dependencies(task_id,blocks_id)
- milestones(id,project_id,date)
- comments(id,task_id,body)
- activity(id,task_id,event,at)
- Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them.
- Acceptance fixture: Launch project: Draft blocks Review; Review blocks Publish; milestone on Friday.

Environment variables

These go in a .env file the app reads at startup. The pack's .env.example is this table as a file · copy it, never commit the filled-in version.

VariableNeededExampleWhere the value comes from
DATA_DIRrequired./data/asanaA new private folder this application creates on first run; never serve it as static files.
SECRET_KEYsecretrequiredreplace-with-a-random-secretGenerate with python -c "import secrets; print(secrets.token_hex(32))" and save only in .env.
APP_MODErequiredindieUse indie for loopback-only personal work. Product mode must refuse to start until owner login and the deployment gates are configured.
SITE_URLrequiredhttp://127.0.0.1:5000The origin used for local forms and links; replace with the chosen HTTPS origin in product mode.

The build, in order

  1. Local foundation and data contract

    Create the runnable local foundation for a small project planner with dependency-aware milestones, including the real schema and acceptance fixture.

    1. Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch.

      Files app.pyrequirements.txt.env.example.gitignore

      terminal
      python -m venv .venv
python -m pip install Flask Flask-WTF python-dotenv waitress tzdata
python -m pip freeze > requirements.txt
python -m flask --app app run --host 127.0.0.1

    2. For database-backed state create schema.sql and db.py using this model: projects(id,name); tasks(id,project_id,title,owner,due_date,status,revision); dependencies(task_id,blocks_id); milestones(id,project_id,date); comments(id,task_id,body); activity(id,task_id,event,at). Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: Launch project: Draft blocks Review; Review blocks Publish; milestone on Friday. Re-running init must not erase data.

      Files schema.sqldb.pymanage.pyfixtures/README.md

      terminal
      python manage.py init
python manage.py seed

    3. Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now.

      Files app.pytemplates/base.htmltest/test_foundation.py

    done when · tick each as it passes
    watch out
    • The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation.
    next phase

  2. Dependency graph

    Dependency graph for Asana: Create projects and tasks with owner, due date and open/done state; validate every referenced project.

    1. Create projects and tasks with owner, due date and open/done state; validate every referenced project.

      Files features/dependency_graph.pytemplates/dependency_graph.html

    2. Add directed blocking edges; run cycle detection inside the update transaction and explain the cycle path.

      Files features/dependency_graph.py

    3. Use Launch project: Draft blocks Review; Review blocks Publish; milestone on Friday. Check: Adding Publish blocks Draft is refused with all three task names. Then check: Deleting a task removes its dependency edges without deleting its neighbors. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser.

      Files test/test_dependency_graph.py

      terminal
      python -m unittest discover -s test
    done when · tick each as it passes
    watch out
    • A dependency is a graph edge, not just a label in a card.
    next phase

  3. Work and milestones

    Work and milestones for Asana: Render a list and board from one task query; show blocked tasks with the incomplete blockers named.

    1. Render a list and board from one task query; show blocked tasks with the incomplete blockers named.

      Files features/work_and_milestones.pytemplates/work_and_milestones.html

    2. Assign tasks to milestones and compute completion from tasks; keep overdue separate from blocked.

      Files features/work_and_milestones.py

    3. Use Launch project: Draft blocks Review; Review blocks Publish; milestone on Friday. Check: Completing Draft unblocks Review in both views after refresh. Then check: A milestone with one of three tasks done shows 1/3, even when filters hide tasks. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser.

      Files test/test_work_and_milestones.py

      terminal
      python -m unittest discover -s test
    done when · tick each as it passes
    watch out
    • Do not claim a simple date list is a resource scheduling engine.
    next phase

  4. Status history

    Status history for Asana: Append comments and assignment/status changes to the task timeline in the same transaction as the mutation.

    1. Append comments and assignment/status changes to the task timeline in the same transaction as the mutation.

      Files features/status_history.pytemplates/status_history.html

    2. Build a weekly project summary listing completed, overdue and blocked tasks; link each count to its underlying rows.

      Files features/status_history.py

    3. Use Launch project: Draft blocks Review; Review blocks Publish; milestone on Friday. Check: Changing an owner produces exactly one dated activity item. Then check: Summary counts match the seeded rows and include no tasks from another project. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser.

      Files test/test_status_history.py

      terminal
      python -m unittest discover -s test
    done when · tick each as it passes
    watch out
    • Keep user-written updates separate from computed status so neither silently overwrites the other.
    next phase

  5. Portable delivery and clean-start proof

    Finish the Asana replacement with a documented first-run path and a recoverable export.

    1. Document prerequisites, every configuration variable, data locations and the three domain workflows: Dependency graph; Work and milestones; Status history. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them.

      Files README.md.env.example

    2. Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for asana. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: Launch project: Draft blocks Review; Review blocks Publish; milestone on Friday. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy.

      Files OPERATIONS.mdscripts/backup.py

    3. Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete.

      Files README.mdverification.md

      terminal
      python -m pip install -r requirements.txt
python -m unittest discover -s test
    done when · tick each as it passes
    watch out
    • Export without an import or restore rehearsal is not verified portability.
what this build does not replace
after v1, if you want it

Need the files? The project pack on the verdict page hands your agent the whole brief · more project management.